Creating SQL Capture Process

To create a new SQL Capture process, choose New from the SQL Capture folder's shortcut menu in the Object Explorer. The New SQL Capture Process wizard will open. In the first page of the wizard, you can choose the following parameters:

• DB Instance - the IDS server, from which you want to capture SQL statements.
• Save in the Repository - check this box if want to save captured SQL statements in the repository.
• Refresh Rate - choose the required SQL retrieval interval. It is important to understand that not all SQL statements executed on the server can be captured. If the statement is executed faster than the specified refresh rate and the client process closes the open SQL statement cursor or immediately executes another SQL statement, than the first statement will not be captured. The purpose of the SQL Capture process is to highlight poorly performing SQL statements - not all SQL statements.

Filter options allow you to specify the user sessions and performance parameters for SQL statement's that you want to capture.

• Filter by User - use this radio button if you want to retrieve only SQL statements executed by specified users. Press Add button to choose user login names.
• Filter by Host - use this radio button if you want to retrieve only SQL statements executed by from specified client host workstations. Press Add button to choose client host workstations.
• Filter by Session ID - use this radio button if you want to retrieve only SQL statements executed by specified client sessions. Press Add button to choose client session IDs.
• Performance Parameters - you can use this grid to enter threshold values for SQL statements performance parameters, such as estimated cost or estimated number of affected rows. It allows you to intercept only problematic poorly performing statements out of the entire universe of SQL statements executed at the database server.

The second page of the wizard provides the following fields:

• Name - give a logical name to this SQL Capture process. It will be displayed under this name in the Object Explorer SQL Capture folder.
• Description - optionally you can describe an SQL Capture process purpose.
• Start after creation - check this box if you want to launch this SQL Capture process immediately after it is created at the Sentinel server. Alternatively, you can use Start Process shortcut menu or button on the SQL Capture process panel to launch it at any time.

Important If SQL Capture process does not record retrieved SQL statements to the Sentinel repository, its sole purpose is to display the captured SQL in real-time within the SSJE GUI panel. When SSJE GUI panel is closed, this SQL Capture process automatically stops execution. If the Save in Repository option for SQL Capture process is selected, Sentinel executes the process in the background even when the GUI panel for this process is closed.