April 1, 2010 at 7:55 am
I am having some i\o buffer problems in one of my instances
I also have several databases that were not upgraded to 90 compatibility mode when they were migrated from SQL Server 2000 to 2005 using
Exec sp_dbcmptlevel @dbname = 'ChangeManagement', @new_cmptlevel = 90 ;
I found this script on this site that you can run against the DB still in 80 compatibility to check for inconsistancies
http://www.sqlservercentral.com/scripts/Compatibility/62093/
I did find some inconsistancies when I ran the script against my 80 Compatibility mode DBs
My question is ... Does anyone know if running
Exec sp_dbcmptlevel @dbname = 'ChangeManagement', @new_cmptlevel = 90 ;
to change these databases to 90 compatibility mode is an online operation? is it disruptive?
These are production databases and I don't know if I need to get a window to do this off-hours.
April 1, 2010 at 10:26 am
Jpotucek (4/1/2010)
I am having some i\o buffer problems in one of my instancesI also have several databases that were not upgraded to 90 compatibility mode when they were migrated from SQL Server 2000 to 2005 using
Exec sp_dbcmptlevel @dbname = 'ChangeManagement', @new_cmptlevel = 90 ;I found this script on this site that you can run against the DB still in 80 compatibility to check for inconsistancies
http://www.sqlservercentral.com/scripts/Compatibility/62093/
I did find some inconsistancies when I ran the script against my 80 Compatibility mode DBs
My question is ... Does anyone know if running
Exec sp_dbcmptlevel @dbname = 'ChangeManagement', @new_cmptlevel = 90 ;to change these databases to 90 compatibility mode is an online operation? is it disruptive?
These are production databases and I don't know if I need to get a window to do this off-hours.
I cannot understand why you want to make such important change to a production database? I think you need to create a development server and move copies to it so you can make the changes run tests, that is run most complex code and then move back to production. The reason 90 compatibility mode may break some of your code that is now running.
Kind regards,
Gift Peddie
April 1, 2010 at 10:32 am
Trying to troubleshoot an I\O buffer problem that froze the Server this morning. I noticed that some of the DBs are not in 90 compatibility mode.. just trying to rule everything out.
April 1, 2010 at 11:30 am
Jpotucek (4/1/2010)
Trying to troubleshoot an I\O buffer problem that froze the Server this morning. I noticed that some of the DBs are not in 90 compatibility mode.. just trying to rule everything out.
I am not sure I\O buffer problem is related to compatibility mode if it is not a known issue because compatibility 80 just prevent the database to use compatibility 90 features. I am running Windows 7 so I don't have access to SQL Server 2000 so just run some tests.
Kind regards,
Gift Peddie
April 1, 2010 at 11:34 am
I believe Gift Peddie is correct. The mode doesn't affect how IO processes, it affects how code/keywords are interpreted.
April 1, 2010 at 11:48 am
Thank you : )
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply