Showing posts with label showing. Show all posts
Showing posts with label showing. Show all posts

Sunday, March 11, 2012

Database at 9.0.3152 but SSMS at 9.0.3042 - Problem?

I've got a SQL 2K5 installation that I have upgraded to 9.0.3152. In SSMS, I see the SQL Server instance showing with the correct version - 9.0.3152. But SSMS (Help->About) shows a version of 9.00.3042. Is this expected or should "Cumulative hotfix package (build 3152) for SQL Server 2005 Service Pack 2 is available" (http://support.microsoft.com/default.aspx/kb/933097/) have upgraded all these to 3152, as well?

Thanks!

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.086.1830.00 (srv03_sp1_rtm.050324-1447)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

There are several ways to check the version level of various components. The easiest seems to be by using Add/Remove Programs. Click on your SQL entry, then uninstall, and then Change. This pops up a nice report showing your machine at the component level and the associated versions. If SSMS is at 3042, you can apply hotfix 3152 and bring it up to date. My guess is that SSMS might not show the hotfix level (only the SP level) and that your box is updated already.

Thanks,

Sam Lester (MSFT)

|||

Really it may not be the easiest way for remote server.

Iа I were you (or if you were I), I would have preferred

SERVERPROPERTY function.


SELECT SERVERPROPERTY('productversion') AS ProductVersion,

SERVERPROPERTY ('ResourceVersion') As ResourceVersion ,

SERVERPROPERTY ('productlevel') AS ProductLevel,

SERVERPROPERTY ('edition') As Edition,

SERVERPROPERTY ('ResourceLastUpdateDateTime') As ResourceLastUpdateDateTime

Shows for me
ProductVersion ResourceVersion ProductLevel Edition ResourceLastUpdateDateTime
9.00.3054.00 9.00.3042 SP2 Developer Edition 2007-02-10 00:39:35.480

Database at 9.0.3152 but SSMS at 9.0.3042 - Problem?

I've got a SQL 2K5 installation that I have upgraded to 9.0.3152. In SSMS, I see the SQL Server instance showing with the correct version - 9.0.3152. But SSMS (Help->About) shows a version of 9.00.3042. Is this expected or should "Cumulative hotfix package (build 3152) for SQL Server 2005 Service Pack 2 is available" (http://support.microsoft.com/default.aspx/kb/933097/) have upgraded all these to 3152, as well?

Thanks!

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services Client Tools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 2000.086.1830.00 (srv03_sp1_rtm.050324-1447)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 7.0.5730.11
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

There are several ways to check the version level of various components. The easiest seems to be by using Add/Remove Programs. Click on your SQL entry, then uninstall, and then Change. This pops up a nice report showing your machine at the component level and the associated versions. If SSMS is at 3042, you can apply hotfix 3152 and bring it up to date. My guess is that SSMS might not show the hotfix level (only the SP level) and that your box is updated already.

Thanks,

Sam Lester (MSFT)

|||

Really it may not be the easiest way for remote server.

Iа I were you (or if you were I), I would have preferred

SERVERPROPERTY function.


SELECT SERVERPROPERTY('productversion') AS ProductVersion,

SERVERPROPERTY ('ResourceVersion') As ResourceVersion ,

SERVERPROPERTY ('productlevel') AS ProductLevel,

SERVERPROPERTY ('edition') As Edition,

SERVERPROPERTY ('ResourceLastUpdateDateTime') As ResourceLastUpdateDateTime

Shows for me
ProductVersion ResourceVersion ProductLevel Edition ResourceLastUpdateDateTime
9.00.3054.00 9.00.3042 SP2 Developer Edition 2007-02-10 00:39:35.480

Saturday, February 25, 2012

Data/Preview windows not showing same data return

When I test my query in the "Data" window (tab), I get a healthy number of
rows returned. When I test under the "Preview" window (tab), I get a tiny
fraction of rows returned. Can someone tell why this is? Perhaps, something
in the "Layout" that I am missing? I'm not even sure how the data I am
getting in the "Preview" window is unique compared to the other data I did
not get.
Thanks in advance for any clues!Here is what might be happening. The preview tab caches data. If the
parameter is not changed it re-uses the data. Look where your .rdl file is
and you should see files with a .data extension. Either delete this file to
force it to hit the database again or just run your report with a different
parameter.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lu" <Lu@.discussions.microsoft.com> wrote in message
news:E1372BDD-F320-4687-9390-F703136400FF@.microsoft.com...
> When I test my query in the "Data" window (tab), I get a healthy number of
> rows returned. When I test under the "Preview" window (tab), I get a tiny
> fraction of rows returned. Can someone tell why this is? Perhaps,
> something
> in the "Layout" that I am missing? I'm not even sure how the data I am
> getting in the "Preview" window is unique compared to the other data I did
> not get.
> Thanks in advance for any clues!|||Thanks, Bruce. I flushed the old data, but this did not resolve the issue.
I forgot to mention that I deployed as well thinking it may have been cached
data. However, the problem also persists on production. I have the
parameters the same on both test preview and the raw query (data tab) and
even in the SQL Srvr Mgmt Studio...the preview and production windows only
retrieve 3 rows of data as opposed to the expected 3,000+ rows of data. It
should also be noted that something must've changed that I didn't catch
because the query was pulling more info than it is now...not all of it, but
was still pulling more than now.
"Bruce L-C [MVP]" wrote:
> Here is what might be happening. The preview tab caches data. If the
> parameter is not changed it re-uses the data. Look where your .rdl file is
> and you should see files with a .data extension. Either delete this file to
> force it to hit the database again or just run your report with a different
> parameter.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lu" <Lu@.discussions.microsoft.com> wrote in message
> news:E1372BDD-F320-4687-9390-F703136400FF@.microsoft.com...
> > When I test my query in the "Data" window (tab), I get a healthy number of
> > rows returned. When I test under the "Preview" window (tab), I get a tiny
> > fraction of rows returned. Can someone tell why this is? Perhaps,
> > something
> > in the "Layout" that I am missing? I'm not even sure how the data I am
> > getting in the "Preview" window is unique compared to the other data I did
> > not get.
> > Thanks in advance for any clues!
>
>