Restore a backup from an older SQL Server into a test database, read the upgrade messages, and check compatibility and integrity.
Incorrect Syntax Near: When Compatibility Level Is the Cause
Incorrect syntax near means the parser met a word it did not expect, and a low compatibility level is one cause. This post reproduces the error, shows how to read and raise the level, and covers the other common causes.
SQL SERVER – 2005 – Change Compatibility Level – T-SQL Procedure
The safe way to change compatibility level in SQL Server 2005: single user mode, sp_dbcmptlevel, then multi user again, and how to check it.
SQL SERVER – 2005 Change Database Compatible Level – Backward Compatibility – Part 2 – Management Studio
How to change database compatible level in SQL Server Management Studio: right click the database, open Properties, then Options, and pick the level you need.
SQL SERVER – 2005 Change Database Compatible Level – Backward Compatibility
Use sp_dbcmptlevel to change the database compatible level, like 80 for SQL Server 2000 or 90 for 2005, plus the three step best practice to do it.