July 19, 2011 at 10:39 am
I have a SQL Server 2008 Instance. I took a database from a SQl Server 2000 instance and restored i to the 2008 instance. I have set the compatibilty mode to SQL Server 2008 (100) and I have run the following against the database:
dbcc checkdb with data_purity
dbcc updateusage('<dbname>')
exec sp_updatestats
The vendor for the application using the database is saying they will not support it until the database is converted to SQL Server 2008. What else do I need to do here?
Thanks,
Kim
July 19, 2011 at 10:46 am
I think it is a 2008 database. As soon as you restore it, the structure converts. If it's set to the compat mode, I'm not sure what else you could do.
July 19, 2011 at 10:58 am
Ask for more details. This is now a sql 2008 DB. I'm sure they can send you a checklist of steps to go through to "complete" the conversion.
It might be as simple as upgrading their own GUI which changes a few tables / columns in the system too!
July 19, 2011 at 2:05 pm
Thank you for the responses. I was able to explain to the vendor with confidence that the database was indeed SQl Server 2008 and they no longer refused to support my issue. They went on to find that the script they sent for the upgrade did not account for our specific installation (which they put in place).
WIN!
Thanks again 🙂
July 19, 2011 at 3:10 pm
kstjacques (7/19/2011)
Thank you for the responses. I was able to explain to the vendor with confidence that the database was indeed SQl Server 2008 and they no longer refused to support my issue. They went on to find that the script they sent for the upgrade did not account for our specific installation (which they put in place).WIN!
Thanks again 🙂
Glad you got it figured out. The "win" is just extra :-D. At some point and with repetition and can come in handy tho!
July 19, 2011 at 4:01 pm
the only other thing you might want to do is the upgrade will create schema for each SQL account and set that as its default schema. As most SQL2000 dbs have dbo as the owner of all objects you should change all default schemas to dbo and drop the schemas created.
---------------------------------------------------------------------
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply