Comments on: SQL SERVER – 2005 Change Database Compatible Level – Backward Compatibility

By: Jwalant Natvarlal Soneji

Jwalant Natvarlal Soneji — Tue, 16 Apr 2013 22:36:45 +0000

100 = SQL Server 2008
110 = SQL Server 2012

By: Mohamed Bijili

Mohamed Bijili — Mon, 21 Jan 2013 06:31:32 +0000

Im using sql server 2005,the Database Compatible Level 90 is not supporting in vb.net , it supports 80 only.

By: sabyasachis86

sabyasachis86 — Tue, 15 Jan 2013 06:34:27 +0000

Pinal Sir,
What is the significance of doing this. I am not able to get… Please reply me…

By: Vipul

Vipul — Wed, 05 Dec 2012 09:26:57 +0000

Hi Gleb

Its not the Database compatiblity i need, Its the SQL SERVER Management studio compatiblity . when i run a script like
DECLARE @var nvarchar(max) = ‘test data’

On a DATABASE any compatiblity level , It does not give error if db is in sql studio 2008.
but it gives error if the DB is on sql server management studio 2005.

so i need a setting for my query window in sql server management studio 2008 to behave like sql server management studio 2005.

Thanks
Vipul

By: Vipul

Vipul — Wed, 05 Dec 2012 09:25:58 +0000

Hi Gleb
Its not the Database compatiblity i need, Its the SQL SERVER Management studio compatiblity . when i run a script like
DECLARE @var nvarchar(max) = ‘test data’

On a DATABASE any compatiblity level , It does not give error if db is in sql studio 2008.
but it gives error if the DB is on sql server management studio 2005.

so i need a setting for my query window in sql server management studio 2008 to behave like sql server management studio 2005.

Thanks
Vipul

By: GLeb

GLeb — Wed, 05 Dec 2012 08:20:09 +0000

–new syntax
ALTER DATABASE test2008
SET COMPATIBILITY_LEVEL = 100

– Valid values of the database compatibility level are 90 (for 2005), 100 (for 2008), or 110 (for 2012).

By: vipul

vipul — Fri, 20 Jul 2012 12:17:08 +0000

Hi i have a similar problem. I am using sql server 2008. i make upgarde scripts for a 2005ver. db. when i execute scripts like Declare @var int =0; they are executed on my environment(sql server 2008) but on client environment which has sql server 2005 installed, it throws error. i know how to correct this. but there any way to make settings of sql server 2008 make us know whether the script will run or not on sql server 2005.

By: Andrew Osiname

Andrew Osiname — Fri, 20 Jul 2012 10:42:54 +0000

I changed my server to SQL 2005 from 2000 using EXEC sp_dbcmptlevel TQM, 90;

It allowed me to use the PIVOT command but caused a strange problem.

On some old stored procecures, a previous developer had written a query like so:

SELECT
s.firstname,
c.carreg,
.s.surname /*notice .s.surname*/

FROM
staff s
INNER JOIN
car c ON c.StaffID = s.StaffID

I normally wouldnt write .s.surname because the table staff was aliased to s not .s

However thats how the code was written.

When i changed the compatibility level to 2005, the stored procedure didnt work anymore and when i changed it back to 2000 – it did…just thought it was worth mentioning.

So i removed the extra .’s from all stored procedures and its all fine but a strange bug…

By: vipul

vipul — Thu, 28 Jun 2012 06:42:04 +0000

Hi i have a similar problem. I an using sql server 2008. i make upgard scripts for a 2005ver. db. when i execute scripts like Declare @var int =0, they are executed on my environment but on client environment which has sql server 2005 installed, it throws error. i know how to correct this. but there any way to make settings of sql server 2008 make us know whether the script will run or not on sql server 2008.

By: viral

viral — Thu, 24 May 2012 23:28:35 +0000

Hi, I am a business analyst working on SQL2000 to SQL2008R2 upgrade. We used Upgrade Advisor to identify the issues which require the code level changes. But how can i make sure if this were all the issues ?

Is there anything which an Upgrade Advisor cannot catch ?

Please help

By: Jonald

Jonald — Tue, 21 Feb 2012 09:54:03 +0000

please help thats my code

By: Jonald

Jonald — Tue, 21 Feb 2012 09:52:56 +0000

‘JONALD
‘when i want to update data,,..the error is “Fialed to Update”

Private Sub btnok_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnok.Click

Connection_open()

cmd = New SqlCommand(” UPDATE TBLNAME SET FirstName = ‘” & txtfirstname.Text & “‘, MiddleName = ‘” & txtmiddlename.Text & “‘, LastName = ‘” & txtlastname.Text & “‘, Program = ‘” & maskedprogram.Text & “‘ where StudentID = ‘” & txtstudentID.Text & “‘ “, conn)

j = cmd.ExecuteNonQuery

If j > 0 Then

MsgBox(“Update success!”)

Else
MsgBox(“Failed to update!”)

End If
connection_close()

txtstudentID.Clear()
txtfirstname.Clear()
txtmiddlename.Clear()
txtlastname.Clear()
maskedprogram.Clear()
txtstudentID.Focus()

End Sub

By: Martin

Martin — Fri, 10 Feb 2012 11:12:39 +0000

I would like to automate (via T-SQL) a backup and restore between a SQL Server 2008 (Production server) and SQL Server 2008 R2 (Report server). I know how to do it via the graphical interface, however I have hard time to figure out via T-SQL

Thanks
Martin

By: joksin

joksin — Fri, 13 Jan 2012 10:20:05 +0000

how to change version of database from 611 to 539

By: Vikas

Vikas — Fri, 09 Dec 2011 05:31:54 +0000

Hi Pinal, I took backup of a database on SQL 2008 R2 server after changing it’s compatibility level back to 90.

Now I want to restore that DB on a SQL 2005 server, is it possible? I tried and it’s giving me error.

Thanks,
Vikas Verma

By: manu

manu — Tue, 20 Sep 2011 18:12:12 +0000

Okay so this is funny.

We have a procedure that uses MERGE statement and works fine in 2008.
One of our clients uses 2005, and it was failing for them.

On our current 2008 Servers, we set the compatibility level to 90 and even 80 later, (in hope of trapping the error because of the merge statement) but the merge procedure compiles and executed fine in each of the cases.

I double checked the compatibility level is sys.databases, and opened up a brand new connection, set SIngle user prior to changing the compatibility level etc.

I am stumped..

What’s going on here ?
Any ideas, insights ?

Manu

By: Sujith

Sujith — Thu, 11 Aug 2011 07:09:56 +0000

Hi Pinal,

Can you please advise me to migrate MS SQL 2000 to another MS SQL 2000 server.. There is some hardware issues, actually we need to move SQL server to another server,, It is having around 95 DBs, so can you please tell me the best way to migrate the server?

Please excuse me if I am posting this on the wrong area..

Thanks you,
Sujith

By: cccp

cccp — Sun, 07 Aug 2011 02:09:28 +0000

Please!!! anyone can help me? why Do i not have level 90 on my sql server 2005? There’s only 7 and 8.

By: Priti

Priti — Mon, 04 Jul 2011 10:17:58 +0000

hi Pinal,
Actually am shifting from sql 7.0 to sql server 2008. but now the problem arises when the formwe DB is restored in latter one.. i tried the sp_dbcmptlevel but in vain.. as 7.0 doed not support 80,90,or 100.. and i have also tried to first restore it to 2005 and executed the cmd and again restore to 2008 but this also not worked/…!!

CAn u plz help by any possible solutionss…

txs in advance… :)

By: rammohan

rammohan — Sat, 02 Jul 2011 06:28:23 +0000

Please help me ….
i am working on JOBBOSS software, with the backend of sql server 2005. where should i get the detailed information which is stored in the database for editing or modification…

By: Miguel

Miguel — Wed, 15 Jun 2011 11:11:48 +0000

Hi,

I wonder if someone would be able to explain why the following 2005 code can run on DB with compatibility mode set to 80 (so 2000) on a SQL2005 server? Since xml is 2005 and doesn’t exist neither this code runs on SQL2000.

declare @test xml
set @test = ”

Is this a “normal” behaviour SQL2005 cpat 80 mode or a feature?

Is there any trick to really set a DB to full compatibility mode 80 (2000) instead of a mixed 2000-2005 mode? All this to make sure devs don’t write 2005 code against a 2000 DB which can be ported into a SQL2000 server. Thanks

Regards,
Miguel

By: madhivanan

madhivanan — Mon, 18 Apr 2011 10:58:16 +0000

Then it is not possible to use try/catch method

By: Ajit Dubey

Ajit Dubey — Fri, 15 Apr 2011 08:30:18 +0000

@vikas sahu

Those number tells you about your edition and service pack details. Run below command and you’ll come to know about it-

SELECT SERVERPROPERTY(‘productversion’), SERVERPROPERTY (‘productlevel’), SERVERPROPERTY (‘edition’)

For more details, please visit-
http://support.microsoft.com/kb/321185

By: Ajit Dubey

Ajit Dubey — Fri, 15 Apr 2011 08:20:29 +0000

@madhivanan.

Unable to do so because I have only two options coming in i.e. 70 & 80. No option of 90.

By: madhivanan

madhivanan — Tue, 12 Apr 2011 08:23:49 +0000

Change the compatibility mode to 90