February 15, 2011 at 1:45 pm
We have a vendor database that is set to Compatibility Level 'SQL Server 2000'. They don't support any level above that and "have no plans to test" any level above 2000.
I'm new to SQL Server but have solid experience with Oracle on both Windows and RHEL. I want to do a good job managing this vendor database and am ready to go command-line with it if I have to. On the other, if I can use SSMS to monitor this one instance (focusing on one vendor database, really), I'd like to do that and not spend a bunch of time building scripts.
What I'm seeing in the SSMS GUI tools is that some of them are disabled by the low compatibility setting for this database. I can set compatibility up to 2008 and, viola!, I get numbers. Set it back to 2000 and, well, no numbers.
Do you have any advice/tricks for monitoring/managing a database in SQL Server 2008 while being forced to keep the compatibility level set to 2000?
Thanks, T
February 15, 2011 at 5:27 pm
Run SQL Server Profiler. Change compatibility level for the database to 2008. Run you reports using GUI. Go back to Profiler and find the query. Do it for your all main tasks. Save the scripts.
Change database compatibility level back to 2000 and use the saved scripts.
February 16, 2011 at 2:53 pm
Good idea. Thanks for the help. -T
February 17, 2011 at 2:11 am
I don’t mean to state the obvious Tim, but your organisation needs to look at replacing this product and this vendor.
SQL Server 2000 is already out of mainstream support.
If the vendor is really refusing to certify their product on anything other than an 11 year old database engine, then the supportability of their product going forward is questionable at best.
February 17, 2011 at 6:17 am
Andy has replied correctly.
Try to have vendor work on their application and make it compatiable to SQL 2008 Directly.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply