January 26, 2010 at 2:26 pm
Hi all:
In reading the BOL topic about Compatibility level, it appears this primarily affects how stored procedures are compiled and little else. Is this true? For instance, would setting the compatibility level to 90 restrict your database columns to only allow data types available in SQL 2005? Even further, would the file format revert to SQL 2005 format and thus make a database interchangeable amongst a SQL 2008 and SQL 2005 instance.
I'm asking this for the sake of discussion. I don't intend to do this.:-)
Thanks,
Del
January 26, 2010 at 4:32 pm
would the file format revert to SQL 2005 format and thus make a database interchangeable amongst a SQL 2008 and SQL 2005 instance.
If a database is attached to SQL 2008 it can only be attached or restored to SQL 2008. SQL can go forward versions but not back versions.
You can restore/attach db's from SQL 2000/2005/2008 to a 2008 instance. 2000/2005 db's can be restored/attached to SQL 2005 but a db from a 2008 instance cannot be attached/restored to a 2005 instance regardless of compatibility level.
January 27, 2010 at 6:29 pm
Compatibility mode affects what commands are available in that database. It is used generally for backward compatibility to allow legacy code written using deprecated code to run on a new version.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
January 27, 2010 at 6:39 pm
Thanks for your input, Jeffrey.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply