Read about updates, corrections, and clarifications for Adaptive Server Reference Manual: Commands.
The reference page for reorg includes this incorrect note:
Replace with:
The Auditing section of the alter table reference page includes this bullet item, which is incorrect:
Add this text to the "Information in extrainfo" column of the Auditing section of the create table reference page:
There are two updates for dump database and dump transaction:
The Parameters section of both dump database and dump transaction include the following:
The 100 and 101 compression levels do not work with compress:: compression_level. Specifying these values causes the command to return an error.
You may, however, continue to use 100 and 101 compression levels with the with compression= parameter.
The maximum file path/name size for a physical device is 127 characters. This limitation is not explicitly stated in the Restrictions subsection of the Usage section of the reference pages for dump database and dump transaction.
The Usage section includes this bullet item:
You cannot supply string and char_variable options to execute the following commands: begin transaction, commit, connect to, declare cursor, rollback, dump transaction, dbcc, set, use, or nested execute commands.
Adaptive Server currently uses a more relaxed list, which includes:
The definitions for the following set options should now read:
Add the following information to the Usage section of the transfer table reference page:
When transfer table runs into an error (such as duplicate key), only the underlying error number is reported, but not the error message. This makes it difficult for a user to understand why the statement was aborted. For example:
Msg 2633, Level 20, State 1 Server 'SYB155', Line 1 TRANSFER TABLE failed to insert a row to table 'my_tab'. The indicated error was 2601. Msg 16025, Level 16, State 1 Server 'SYB155', Line 1 TRANSFER TABLE my_tab: command failed with status 2633.
To retrieve the error message, manually query master..sysmessages. For example, if 2601 is your error number, enter:
select * from master..sysmessages where error = 2601
See the Troubleshooting Guide for more information about error 2601.