Displays or sets the maximum number of suspect pages that the SAP ASE server allows in a database before marking the entire database suspect.
sp_setsuspect_threshold [dbname [, threshold]]
sp_setsuspect_threshold pubs2, 5
sp_setsuspect_threshold pubs2
sp_setsuspect_threshold
You must be in the master database to set the suspect escalation threshold with sp_setsuspect_threshold.
If you do not specify the number of pages, the SAP ASE server displays the current and configured settings. The current setting is the one that was in effect the last time recovery was executed in the database. The configured setting is the one that is in effect the next time recovery is executed in the database.
The permission checks for sp_setsuspect_threshold differ based on your granular permissions settings.
Setting | Description |
---|---|
Enabled | With granular permissions enabled, you must be a user with own database privilege on the database to set the escalation threshold. Any user can execute sp_setsuspect_threshold to display settings. |
Disabled | With granular permissions disabled, you must be a user with sa_role to set the the escalation threshold. Any user can execute sp_setsuspect_threshold to display settings. |
Values in event and extrainfo columns from the sysaudits table are:
Information | Values |
---|---|
Event | 38 |
Audit option | exec_procedure |
Command or access audited | Execution of a procedure |
Information in extrainfo |
|