Is there a clear and methodological method to change the compatibility mode of a databases individual Tables & Columns? A 3rd party database was upgraded and migrated to SQL 2005, the SQL Server Compatibility is at the correct setting, but there are tables/columns contained within the new db that have retained old compatibility settings.
Tell me more
×
Database Administrators Stack Exchange is a question and answer site for
database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.
|
|
Compatibility levels are set at the database, not at the table or column. You might be thinking of collations, which are set at the column level. You can't simply change the collation on those objects - you have to build new objects with the right collations and push the data into them. You might also be thinking of deprecated datatypes like text, ntext, image, or vardecimal. You don't have to change those yet, but you'll have to fix them before a future SQL Server version. |
|||
|
|