|
|
Posted by Erland Sommarskog on 10/02/75 11:43
Peter Nurse (PtrNrs@yahoo.com.au) writes:
> I completely uninstalled & reinstalled SS 2005 (rather than upgrading
> from SS 2000) and then attached my databases. Problem disappeared.
> I'm sure the problem was to do with msdb which was
> SQL_Latin1_General_CP1_CI_AS but now is Latin1_General_CI_AS.
>
> My databases remain SQL_Latin1_General_CP1_CI_AS but it no longer seems
> to be a problem.
So you got everything working? That's great to hear!
Uninstalling SQL 2005 and reinstalling a fresh install, was probably the
only way out. I was completely baffled to see SELECT serverproperty() to
fail. It seemed impossible to understand what was going on. But my guess
is that the system databases were SQL_Latin1_General_CP1_CI_AS originally,
but that the upgrade somehow changed them to Latin1_Genereal_CI_AS. I don't
think that msdb was the main culprit, but rather master itself.
I will play around a little, and see if I can reconstruct at least part of
the problem. And at least I will report it internally to Microsoft, so that
they know about it. It's difficult to submit a proper bug report, though,
as that would require a complete repro. I have a feeling that the origin of
the problem may have been some funky setting in your original master
database, and that is difficult to recover now.
As for the missing GetDBVersion, that appears to be related to Reporting
Services, and it came from a different spid that ran queries for the
Database Properties dialog.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|