Testing all procs before upgrading to Compatibility Level 90

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by Luiz Barros » Testing all procs before upgrading to...

Testing all procs before upgrading to Compatibility Level 90

Rate Topic

Display Mode

Topic Options

Author

Message

Luiz-458831

Posted Monday, February 04, 2008 9:09 AM

Valued Member

Group: General Forum Members
Last Login: Wednesday, May 08, 2013 3:35 PM
Points: 73, Visits: 445

Comments posted to this topic are about the item Testing all procs before upgrading to Compatibility Level 90

Post #451202

GSquared

Posted Thursday, March 27, 2008 10:58 AM

SSCoach

Group: General Forum Members
Last Login: 2 days ago @ 1:45 PM
Points: 15,442, Visits: 9,572

Clever. I like it. This'll come in useful to me on the project I'm doing next week. Thanks.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

Post #475592

SQLRNNR

Posted Tuesday, September 01, 2009 11:36 AM

SSCoach

Group: General Forum Members
Last Login: Today @ 9:30 AM
Points: 18,857, Visits: 12,441

Thx - this will prove useful in the new environment i just inherited.

Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server 2008

SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp

Post #780923

K Foster

Posted Friday, December 24, 2010 11:29 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, May 24, 2013 1:44 PM
Points: 122, Visits: 201

I think I am missing something here... The database is compatibility level 80 and the script tries to create a proc in that database and expects it to trap the ones that error out because they aren't compatible with level 90. If compatibility level applies to the whole database then how can it error out on a proc that isn't being created on a level 90 database? I've got a stored procedure in a level 80 database that I believe should be incompatible in level 90 and above because no WITH keyword is with the locking hint, something like...

Create procedure dbo.test_with
as
select col1, col2, col5 from dbo.table nolock
go

When I run the script it doesn't report the procedure as a problem.

Either I don't understand something I need to do with the script or I don't understand the compatibility differences here
http://msdn.microsoft.com/en-us/library/bb510680.aspx

Can anyone enlighten me about this?

Thanks.

Post #1039151

K Foster

Posted Friday, December 24, 2010 12:36 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, May 24, 2013 1:44 PM
Points: 122, Visits: 201

Since my last posting I've found an article that says that some of the table hints including nolock are exceptions to the 'WITH' keyword rule.

Thanks.

Post #1039161

« Prev Topic | Next Topic »

Permissions