
5-20 Implement: Making Required Application Changes
If Your Current Version is 4.x, 10.x, or 11.0.x Adaptive Server Enterprise 11.5
Changing Reserved Words in Your Applications
Sybase-provided tools such as the reserved words check option of
the upgrade program for UNIX and the stored procedure
sp_checkreswords allow you to check for database name conflicts in
Adaptive Server both before and after upgrade. However, you must
change the references to these objects in your applications as well to
prevent processing failures.
Checking for reserved words in your applications may be a laborious
process. You can write your own scripts to perform this check. An
easier option may be using third-party tools such as the Cyrano
Migration Pack which contain utilities to help you identify potential
problems before upgrading. See Appendix A, “The Cyrano
Migration Pack” for information about the migration tools created
by Cyrano for Sybase migration.
Avoiding Future Reserved Word Conflicts
To avoid having to search for reserved words in new releases, you
can adopt a naming convention where you use an initial and
underbar with every object name. For example, a table named user
can be written u_user, and a column in the table named address can be
written u_address.
Using the set Command to Keep Object Names
If you choose not to change object names, you can use the
set
quoted_identifier
option. You must add the following set command to all
your applications, putting quotes around all keywords, when you
issue Transact-SQL statements. For example:
set quoted_identifier on
select “user” from
table_x
Table 5-5: New reserved words in 11.5
activation identity_start
connect membership
consumers passwd
exclusive proxy
external session
Comentários a estes Manuais