Hi everybody:
We have recently migrated our DDBB from SQL 2000 to SQL 2005 in several Servers. We have 2 DDBB per Server and the size of mdf files are between 10 and 40 GB.
We put Compatibility Level in 90 in SQL 2005 but when we arrive at work we see that our Maintenace Plans failed because the Compatibility Level of one of Data Bases changed to 70.
We have a Trace executing the whole day registrying the execution of stored procedure 'sp_dbcmptlevel' but in despite of Compatibility Level changes, the Trace does not registry anything.
Has anyone passed before me for this situation? Thank you in advance and greetings,
Nuria
After migrating (backup/restore or detach /attahc) to SQL Server 2005 have u changed the Comaptibility level? By default, the compatibility level will be 80. What was the compatibility leve of this database in sql 2000? check that. I assume that it was 70
Madhu
|||your sql 2000 db probably would have had a compatability of either 80 or 70 (65,60 are not supported in sql 2005).......so once you restore it in sql 2005 it would be in the default compatability level as it was in sql 2000 unless you manually change it.......
|||Yes, after migrating (attach in our case) to SQL 2005 we have changed the Compatibility Level to 90.
Not sure what was the Compatibility Level before migrating of this specific Server because we have 52 Servers in total; some of them had 65, others had 70 and other had 80.
The amazing thing is that Compatibility Level changes alone from 90 to 70.
|||Yes, after migrating (attach in our case) to SQL 2005 we have changed the Compatibility Level to 90.
The amazing thing is that Compatibility Level changes alone from 90 to 70.
No comments:
Post a Comment