Keyword Conflicts

Migrate your Sybase databases to a test Microsoft database and fully test your applications and administrative procedures against the test Microsoft database, including stress testing, before you transfer the entire production system to Microsoft SQL Server.

Review your T-SQL statements and the names of SQL Server objects for keyword conflicts before transferring your objects and data to Microsoft SQL Server.

The following table lists Sybase System 11 keywords that will not function in Microsoft SQL Server and keywords that are reserved by Microsoft SQL Server. If your T-SQL statements use any of the listed keywords, replace them with other words before you migrate your Sybase database to Microsoft SQL Server.

Sybase System 11 keywords Microsoft SQL Server reserved keywords
ARITH_OVERFLOW

AT

CHAR_CONVERT

ENDTRAN

ERRORDATA

MAX_ROWS_PER_PAGE

NATIONAL

NOHOLDLOCK    

NUMERIC_TRANSACTION

ONLINE

PARTITION

REPLACE

ROLE

ROWS

SHARED

STRIPE

SYB_IDENTITY

SYB_RESTREE

UNPARTITION

USER_OPTION

USING

CASE

COALESCE

COMMITTED

CROSS

CURRENT_DATE

CURRENT_TIME

CURRENT_TIMESTAMP

CURRENT_USER

DISTRIBUTED

DROP

FLOPPY

FULL

IDENTITY

IDENTITYCOL

INNER

INSENSITIVE

JOIN

LEFT

NOCHECK

NULLIF

OUTER    PIPE

REPEATABLE

REPLICATION

RESTRICT

RIGHT

SCROLL

SERIALIZABLE

SESSION_USER

SYSTEM_USER

TAPE

THEN

UNCOMMITTED

UPDATETEXT

WHEN