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.

  • Can you describe exactly how you've determined that certain tables and columns have old compatibility settings? – Aaron Bertrand Feb 10 '12 at 23:16
  • 3
    I'm a bit confused by this question, since compatibility level is a database setting. Unless you mean there are columns with different collations (character encodings) that you want to change? – Simon Righarts Feb 11 '12 at 6:29

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.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.