Showing posts with label compatibility. Show all posts
Showing posts with label compatibility. Show all posts

Thursday, March 22, 2012

changing the compatibility level

Hi

I am migrating from sql server 2000 to sql server 2005.

When i do back up and Restore of the databases the compatibility level remains 80 (2000).

my concern is

1) should i change the compatibility level to 90 (2005)

2) Am i missing out any thing if i dont change the compatibility level

3) What are the issues that can come up if changed to 90 (2005)

Please reply .I am in a fix

Thanks in advance

If you still have the original SQL 2000 server/database, don't kill it yet

Run the SQL 2005 Upgrade Advisor on it and it'll give you a list of "errors", and "warnings" if you upgrade to 2005 (Errors are must-fix)

You can decide for yourself if # of errors is huge enough to keep the new DB in 80 mode; if not I suggest 90 mode (we did that, don't require restart either)

But honestly, I can only believe MS' words on that SQL2005 IS BETTER, as I don't have any benchmark comparison

Top 30 features of SQL 2005

http://www.microsoft.com/sql/prodinfo/features/top30features.mspx

sql

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...b;en-us;271566
Cheers
AD
"Don Kitchen" <donkitchen@.gmail.com> wrote in message
news:1110230850.065960.319130@.g14g2000cwa.googlegr oups.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!
>

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/defaul...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!
>

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!
>