SQL 2000 DB with 6.5 Compatibility Level in EM 2005
-
Hello,
I can not see objects for SQL 2000 databases with 6.5 compatibility level when connecting from SQL Server Management Studio (SQL Server 2005)
I can see and expand containers for all other databases on the servers in Object Explorer, but SQL 2000 Databases with 6.5 compatibility level on both Windows 2000 and 2003 servers do not have plus in Object Explorer and do not show content.
I did not find any mention of it in both Object Explorer articles in 2005 CTP BOL
Yelena
Regards,Yelena Varsha
-
This was removed by the editor as SPAM
-
I can only confirm the problem with SQL Server 2005 April CTP English Developer X64 Edition, running on Windows XP 64-bit. I would recommend you to register a bug a MSDN Product Feedback center, or at betaplace if you are a registered beta tester. Give a link to the bug here and I can add feedback to it as well.
-
I did a bit more of digging through BOL and found this on the topic about sp_dbcmptlevel, which is the system stored procedure for viewing and changing database compatibilit levels:
"The 60 and 65 values are deprecated and will be removed in a future release."
Interesting, but should not affect Management Studio.
"SQL Server Management Studio and SQL Server Management Objects (SMO) do not support compatibility level 60. If you use SMO or Management Studio with a database set to compatibility level 60, some operations will produce errors."
Seems to me that not only does it affect compatibility level 65 as well, it also does more than "produce errors for some operations", since it does not even allow us to navigate the database. I also noted that when creating a new database in Management Studio it is not possible to set the compatibility level lower than 70. So I am guessing this is expected behaviour, but the documentation is lagging behind. It will be interesting to see if there are more info in the June CTP.
You could still open a bug though, they will just close it if it is already fixed.
-
Chris,
Thanks a lot for your research. Actually, my 6.5 compat level database is a vendor-supported database, I will notify them to. Will let you know more later. I have a class today, just checked messages during the break
Yelena
Regards,Yelena Varsha
-
Great, I'll keep an eye out. I'm also downloading June CTP right now, so when that is done and installed I can see if there is any change there. Won't be until tomorrow evening though, since I have a presentation on SQL Server 2005 tomorrow morning and will most probably break something if I try to move to June CTP before that..
-
Chris,
Hope your presentation is successful. I will wait then till you let me know if June cTP fixed the issue and if not then I will report it.
Yelena
Regards,Yelena Varsha
-
Yelena,
Thanks, the presentation did go very well, although I had to cut a little material at the end on-the-fly since I did not have time for it. Got caught up demonstrating CLR integration..
Anyway, I just tested with June CTP. Same result, except now the node for the database in compatibility level 65 says "foodb (6.5 Compatible)", so it is clearer why it can not be expanded. Haven't really looked hard in the docs for this, but the topic for sp_dbcmptlevel had not changed so I think some feedback on that could be helpful.
-
Chris,
Submitted those findings to both our Microsoft Premier Support and Application Vendor
Regards,Yelena Varsha
-
Unfortunately I do not think Support wants to have anything to do with Yukon yet. Maybe if you have a very good relationship with them.
Otherwise I would suggest placing a bug or at least suggestion at Product Feedback center and/or Betaplace. In what ways will this be a problem for you? I have a hunch that this is not a bug as such, since I think the simple answer is that SMO (and therefore Management Studio) will not be able to handle 60 or 65 databases. So the best we can achieve is probably an updated documentation that says this.
-
Hi,
I am supposed to escalate all issues through our Premier Support point-of-contact unless I am submitting the issue as an individual, not as a company employee. I may do that as well.
How it affects me? I am what you would call an Application DBA. We have several applications supported by our department that were developed in earlier versions of SQL Server. Some are vendor-supported and some are not, for example if the vendor was out of business 10 years ago. Currently those apps are on SQL 2000, but with efforts, I would say, compat level 6.5. It is OK if I will not see those databases in Management Studio, I can always terminal services the server itself and use 2000 EM, just is not that convenient. It may be easier then changing the level and revalidating the whole thing.
Yelena
Regards,Yelena Varsha
-
Have you tried SQLCMD? It is a very good improvement on the older isql and osql command line tools, and if you are used to using Query Analyzer with T-SQL ddl and more it should not be very difficult to use for 65 compatibility level databases.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply