If you plan to use sqlupgrade to perform the upgrade process, you do not have to check for reserved words as a separate step. In sqlupgrade, you can check for reserved words at the start of the upgrade process, and then continue with the upgrade if no problems are found.
If you plan to use sqlupgraderes to perform the upgrade process using a resource file, you can run sqlupgrade first to identify reserved word conflicts and other potential upgrade eligibility problems. You can specify that you do not want the upgrade to proceed even if no problems are found.
If you use either sqlupgrade or sqlupgraderes, they automatically install new reserved words and sp_checkreswords, a stored procedure used to detect and display any identifiers in your existing databases that conflict with reserved words in the new database. You can then run the new version of sp_checkreswords at anytime while preforming pre-upgrade tasks.
You must use the sp_checkreswords
stored procedure from the new version of Adaptive Server to verify
that the old installation of Adaptive Server does not use any reserved
words that have been introduced with the new server.
Checking for reserved words generates a list of identifiers that conflict with reserved words, and the owners of those identifiers, in the file $SYBASE/$SYBASE_ASE/init/logs/sqlupgradeMMDD.nnn. Review this file to determine which identifiers must be changed.
