dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Enterprise
Expertise: Intermediate
Oct 24, 2001

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Avoiding Trouble with Lower Compatibility Modes


If you have a database that's been upgraded from SQL Server 6.5 to a newer version (like 7 or 2000), but it's still in compatibility mode 65, you can't use keywords that don't exist in this compatibility mode. One example of such a keyword is TOP. Look at the following SQL statement:
 
SELECT TOP 10 * FROM My65Table ORDER BY 1

If this statement is executed in a database with compatibility mode 65, the following error message will be generated:
 
Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near '10'.

To use TOP with a table in the upgraded 6.5 database, execute the command from another database in a higher compatibility mode, i.e. master:
 
USE master
GO

SELECT TOP 10 * FROM <upgraded65database>.dbo.My65Table 
ORDER BY 1
Christoffer Hedgate
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
×
We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.
Thanks for your registration, follow us on our social networks to keep up-to-date