Showing posts with label loaded. Show all posts
Showing posts with label loaded. Show all posts

Thursday, March 29, 2012

Direct Link to reports

Hi There,

I have recently upgraded to report Server 2005. I used to have a webpage that loaded a number of reports into different frames to give real time statistics for an IT Service Desk.

In the new version if try and link directly to the report (By right clicking a report and taking the link) the report loads with out any of the toolbars etc at the top as i need it, however it does not refresh and seem to be cached data.

Has anyone got any ideas how to resolve this problem, in short all I need is a way to directly view the report losing all the toolbars etc on the top and just displaying the data.

This has been driving me mad so if anyone could help i would be really grateful!

Many thanks

Gerard

YOu can definitely do this but not "by rightclicking on a report and taking the link". That's going to get you the origin of the report invocation in report *manager* (by default, http://<yourserver>/reports) when what you want is the link to the report in the report *server* (by default, that would be http://<yourserver>/reportserver).

See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1795172&SiteID=1 .

There is plenty of information on this in the helpfile -- just look for topics that mention "URL Access".

Friday, February 17, 2012

Different @@version

I have 2 machines, both that I _thought_ were loaded with the same
version, but when I do select @.@.version on the two I get different
results:
1.
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Cop
yright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows
NT 5.2 (Build 3790: )
2.
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Cop
yright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Notice how 1 doesn't say Service Pack 1. Both should have SP4 on them.
WHat is the difference?
Darin
*** Sent via Developersdex http://www.codecomments.com ***> Notice how 1 doesn't say Service Pack 1.
That is the service pack of the operating system, not the SQL Server instanc
e. The interesting part
is:
> Microsoft SQL Server 2000 - 8.00.2039
You can now map the build number to the service pack (Aaron has an article o
n this at
www.aspfaq.com). You can also use the SERVERPROPERTY() function to get the s
ervice pack from your
SQL Server.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Darin" <darin_nospam@.nospamever> wrote in message news:OV95wYneGHA.4840@.TK2MSFTNGP03.phx.gb
l...
>I have 2 machines, both that I _thought_ were loaded with the same
> version, but when I do select @.@.version on the two I get different
> results:
> 1.
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
> May 3 2005 23:18:38
> Cop
> yright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows
> NT 5.2 (Build 3790: )
> 2.
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
> May 3 2005 23:18:38
> Cop
> yright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows
> NT 5.2 (Build 3790: Service Pack 1)
> Notice how 1 doesn't say Service Pack 1. Both should have SP4 on them.
> WHat is the difference?
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***

Different @@version

I have 2 machines, both that I _thought_ were loaded with the same
version, but when I do select @.@.version on the two I get different
results:
1.
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Cop
yright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows
NT 5.2 (Build 3790: )
2.
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Cop
yright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Notice how 1 doesn't say Service Pack 1. Both should have SP4 on them.
WHat is the difference?
Darin
*** Sent via Developersdex http://www.developersdex.com ***> Notice how 1 doesn't say Service Pack 1.
That is the service pack of the operating system, not the SQL Server instance. The interesting part
is:
> Microsoft SQL Server 2000 - 8.00.2039
You can now map the build number to the service pack (Aaron has an article on this at
www.aspfaq.com). You can also use the SERVERPROPERTY() function to get the service pack from your
SQL Server.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Darin" <darin_nospam@.nospamever> wrote in message news:OV95wYneGHA.4840@.TK2MSFTNGP03.phx.gbl...
>I have 2 machines, both that I _thought_ were loaded with the same
> version, but when I do select @.@.version on the two I get different
> results:
> 1.
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
> May 3 2005 23:18:38
> Cop
> yright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows
> NT 5.2 (Build 3790: )
> 2.
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
> May 3 2005 23:18:38
> Cop
> yright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows
> NT 5.2 (Build 3790: Service Pack 1)
> Notice how 1 doesn't say Service Pack 1. Both should have SP4 on them.
> WHat is the difference?
> Darin
> *** Sent via Developersdex http://www.developersdex.com ***