SAP ASE version 16.0 introduces changes to system tables.
Column Name | Value |
---|---|
class | 43 |
object | dbid (database ID) |
object_info1 | Starting logical page ID |
object_info2 | Ending logical page ID |
int_value | Last encrypted logical page ID on one storage allocation |
Name | Datatype | Description |
---|---|---|
colid | smallint | Ordering number of trigger. The default is 0. |
constrid | int | Trigger ID. |
tableid | int | ID of the table on which the trigger is declared. |
error | int | Not used for triggers. |
status | int |
|
spare | int | Unused |
Hex | Description |
---|---|
0x00000001 | Indicates whether the database is encrypted or not. |
0x00000002 | The database is being encrypted, and the encryption is still in
progress. |
0x00000004 | The database is being decrypted, and the decryption is still in
progress. |
0x00000008 | The database is only partially encrypted, either due to an error or
because the process was suspended by the user. |
0x00000010 | The database is only partially decrypted, either due to an error or
because the process was suspended by the user. |
In SAP ASE 16.0, the first trigger created on a table for delete, insert, and update operations, where the trigger is created without the order clause (or order 0) is associated with the table in one of the above columns in sysobjects.
The second and subsequent triggers created for a given action are associated with the table through a row in syscontraints. In addition, any trigger with order 1 or greater always uses sysconstraints for the table/trigger association.