Cached SQL drilldown

Using the Cached SQL drilldown

Note: This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions.

On ASE 16 or later the Cached SQL drilldown provides access to details about cached SQL statements and makes it easy to edit or optimize them.

To display the Cached SQL drilldown

Click Users or press Ctrl + U.

Click Cached SQL tab

The top pane displays a grid that shows the cached SQL statements from monCachedStatement monitoring table on ASE 16 or later.

The bottom pane displays the selected cached SQL statement.

Tip: Click the Toad icon to edit the statement in Toad for SAP or click the Optimizer icon to tune the statement in SQL Optimizer for SAP ASE.

User Locks drilldown

Using the User Locks drilldown

The User Locks drilldown provides access to information about the number of lock waits that exceed the Lock Wait threshold, the number of locks in use, and the number of deadlocks detected on the ASE.

To display the User Locks drilldown

Click Locks .

Note: You can also select View | Go To | Locks

Data in the User Locks/Dead Locks drilldown

The Locks/Deadlocks drilldown displays three pages, each of which can be opened by selecting its associated tab.

• Users

• Objects

• Dead Locks

The Users and Objects pages display a grid and Summary and Detail sub-pages. The Dead Locks page displays a Dead Locks grid and User Holding and User Waiting panels.

Threshold Event Log

Note: This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions.

On ASE 16 or later the Threshold Error Log drilldown provides access to details about threshold error messages.

To display the Threshold Error Log drilldown

Click Event Log or press Ctrl + R.

Click Threshold Event Log Tab

Note: In order to use Threshold Event Log the following configuration parameters need to be enabled:

• allow resource limits: to enable collection of resource limits

• enable monitoring, threshold event monitoring, set threshold event max messages: to enable the monitoring table monThresholdEvent collection of data

The top pane displays the limits on the number of server resources set by the user using sp_add_resource_limit procedure.

The bottom pane displays historical threshold event data for the resource limit selected in the top pane.

Change Event Log

Note: This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions.

On ASE 16 or later the Change Event Log drilldown provides access to details about changes in configuration.

To display the Change Event Log drilldown

Click Event Log or press Ctrl + R.

Click Change Event Log Tab

Prerequisites for Change Event Log

The following error messages may be displayed:

"Database sybsecurity not installed. Please install it and enable the audit system"

• sybsecurity database must be installed in order to collect ch_events data

"Configuration history tracking not enabled"

• execute sp_audit "config_history", "all", "all", "on" to enable configuration history tracking

"Auditing not enabled"

• execute sp_configure 'auditing', 1 to enable auditing

"View ch_events not created"

• execute sp_confighistory create_view to create ch_events