Hi,
I work with database administration and I migrated some databases from 2000 to 2005 (simply backup and restore options).
I have tested issues about compatibility. The idea is migrating without update the application.
However, I have already seen some problems with compatibility. After migration, all databases stay with compatibility 80 inside de environment 2005 to avoid problems as, for exemple, the sintax to use hints, with 2005 the with clause isn't opptionaly.
The problem is that somethings isn't ok this way. We can't extract reports as disk usage, backup and restore events etc or generate diagrams for databases with compatibility 80 inside sql management studio.
The reccomendation is change de level for 90, repeat the action and after came back for 80 but we can't do this without impact the current activities. Do you know others problems with databases level 80 and 2005? I read that it's recommended that all databases are updtade for level 90, so I should update my application for changging. What do you think about this?
Thanks,
Karine.
If you want the full features of SQL 2005 Management Studio, then you need to set db compatibility for the database to 90. If not updating your app is more important, then keep it at 80. There's a lot of really cool new UI features and other functionality that depend on compat being at 90, so if it's possible to change your app, I'd do it. Just my opinion.|||Thanks Greg, but do you know some documentation or paper that show or list UI features couldn't be used with database level (80) inside sql management studio?
No comments:
Post a Comment