major changes

[CNTower]

Are there any major changes to the actual SQL language such that older scripts will cause errors?

i.e. is there 100% backward compatibility with older versions of sqlserver?

 

[gmmastros]

Unfortunately, there is not 100% compatibility with older versions of SQL Server unless you use 'compatibility mode'.


Look up [!]sp_dbcmptlevel[/!] in Books On Line

Or here:

http://msdn2.microsoft.com/en-us/library/ms178653.aspx

-George

Strong and bitter words indicate a weak cause. - Fortune cookie wisdom

 

[mrdenny]

Older DML should continue to work fine. The problem you will run into is that some of the commands have changed. For example BACKUP DATABASE used to be called DUMP DATABASE. sp_grantlogin is now CREATE LOGIN.

If you use system tables they can change between versions.

In SQL 2000 and SQL 7 in the sysusers table the roles column held the first role that the login was a member of. In SQL 2005 that column is always null.

Your regular SELECT, INSERT, UPDATE and DELETE commands should continue to work fine. It's the calls to the system objects and the DDL commands that have changed for the most part.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[SQLSister]

I do belive that if you used the oldstyle joins you may have problems in 2005. These are ones without explicitily using the word join in them. If you did this with outer joins, these are a problemin 200 as well as they do not correctly resolve and give the worng data in return.

Questions about posting. See faq183-874