Friday, February 10, 2012

Changing database compatibility from 70 to 80

Hi all. I wanted to know if a database running on SQL Server 2000 SP3a
with a database compatibility level of 70 can be changed to 80 without
any problems. This is a database that was originally built with SQL
Server 7.0. I'm assuming that over time as the DB itself was moved to
SQL Server 2000, the compatibility level was never upgraded.
The reason that I want to change the compatibility level from 70 to 80
is because I need to use the LIKE statement in a table query. It turns
out the LIKE statement uses COLLATE behind the scenes, which is
specific to 80.
Based on what I've read in the SQL Server Books Online, it seems that I
should be able to change this without any problems. I wanted to see
what others think from personal experience (if possible) before I went
and did this.
Any help is greatly appreciated!I've seen many troubles on untidy applications and JDBC apps with regard to
this. Check this KB, just in case. Sorry if redundant:
http://support.microsoft.com/default.aspx?scid=kb;en-us;271566
Cheers
AD
"Don Kitchen" <donkitchen@.gmail.com> wrote in message
news:1110230850.065960.319130@.g14g2000cwa.googlegroups.com...
> Hi all. I wanted to know if a database running on SQL Server 2000 SP3a
> with a database compatibility level of 70 can be changed to 80 without
> any problems. This is a database that was originally built with SQL
> Server 7.0. I'm assuming that over time as the DB itself was moved to
> SQL Server 2000, the compatibility level was never upgraded.
> The reason that I want to change the compatibility level from 70 to 80
> is because I need to use the LIKE statement in a table query. It turns
> out the LIKE statement uses COLLATE behind the scenes, which is
> specific to 80.
> Based on what I've read in the SQL Server Books Online, it seems that I
> should be able to change this without any problems. I wanted to see
> what others think from personal experience (if possible) before I went
> and did this.
> Any help is greatly appreciated!
>

No comments:

Post a Comment