|
When a backup of a SQL 2000 database is restored as a SQL 2005 database it normally comes up with a property compatibility level of 80. If a script was applied to this using SQL 2005 TQL, would it still parse? We have a supplier who repeatedly sends scripts written in SQL 2005 not SQL 2000 which is the database version. I am trying to find any reasonable explanantion as to why they should do this on so many occasions
(comments are locked)
|
|
Why they do it is simple: they have poor quality control. It also ought to make you think that you could move this db into SQL 2005 mode without issues. If I set one of my test SS2K8 databases to 80 mode, it still compiles and executes 2005/2008 based scripts with CTEs. My guess is that it is forward compatible. 'Poor quality control' I thought this was the case but, before I waded in at the project board, I thought I'd better check I had not missed anything. We are moving it to SQL 2005 as soon as we can
Oct 30 '09 at 07:31 AM
hodkinss
(comments are locked)
|
