InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 23 May 2013 07:54:42 GMT20http://www.sqlservercentral.com/Forums/Topic451202-1153-1.aspxSince 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.Fri, 24 Dec 2010 12:36:20 GMTK Fosterhttp://www.sqlservercentral.com/Forums/Topic451202-1153-1.aspxI 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_withasselect col1, col2, col5 from dbo.table nolockgoWhen 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 herehttp://msdn.microsoft.com/en-us/library/bb510680.aspxCan anyone enlighten me about this?Thanks.Fri, 24 Dec 2010 11:29:09 GMTK Fosterhttp://www.sqlservercentral.com/Forums/Topic451202-1153-1.aspxThx - this will prove useful in the new environment i just inherited.Tue, 01 Sep 2009 11:36:45 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic451202-1153-1.aspxClever. I like it. This'll come in useful to me on the project I'm doing next week. Thanks.Thu, 27 Mar 2008 10:58:23 GMTGSquaredhttp://www.sqlservercentral.com/Forums/Topic451202-1153-1.aspxComments posted to this topic are about the item [B]<A HREF="/scripts/Compatibility/62093/">Testing all procs before upgrading to Compatibility Level 90</A>[/B]Mon, 04 Feb 2008 09:09:35 GMTLuiz-458831