sp_setsuspect_threshold

Displays or sets the maximum number of suspect pages that the SAP ASE server allows in a database before marking the entire database suspect.

Syntax

sp_setsuspect_threshold [dbname [, threshold]]

Parameters

Examples

Usage

There are additional considerations when using 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.

Permissions

The permission checks for sp_setsuspect_threshold differ based on your granular permissions settings.

SettingDescription
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.

Auditing

Values in event and extrainfo columns from the sysaudits table are:

InformationValues
Event

38

Audit option

exec_procedure

Command or access audited

Execution of a procedure

Information in extrainfo
  • Roles – Current active roles

  • Keywords or options – NULL

  • Previous value – NULL

  • Current value – NULL

  • Other information – All input parameters

  • Proxy information – Original login name, if set proxy in effect

Related reference
sp_forceonline_db
sp_forceonline_page
sp_listsuspect_db
sp_listsuspect_page
sp_setsuspect_granularity