REQUESTS page
The Manager REQUESTS page provides information about all current requests for service including:
• Inbound requests through a TDV data service.
• Outbound requests against physical data sources.
• Internal requests against internal views.
Summary information is displayed at the top of the REQUESTS page, and information about individual request is displayed in the table. Operational information about queued, in process, and recently completed requests gives the administrative user an idea about what requests are taking inordinate amounts of time or memory resources to complete.
This section includes:
Some of the information displayed on the REQUESTS page is controlled by the following Studio configuration parameters:
• Request Events
• Requests
Requests are removed from the table periodically, based on the Studio Manager configuration setting: Request Purge Period
The default setting purges requests every 5 minutes.
REQUESTS Summary Information
The REQUESTS page provides the following summary information:
• Status - Aggregated status of all requests can be OK, Warning, Error, or Unknown. A single warning or error supersedes display of a status of OK.When failed requests or waiting requests are present, a count of those warnings or errors will be shown.
• Waiting Requests - Current number of requests waiting in the queue due to memory constraints.
• Waiting Requests Threshold - An event trigger threshold that causes an event. The event can be used for notification.
• Server Requests (Active and Total) - The number of currently active requests, and the total number of requests made to the server since the server was started.
• Data Source Requests (Active and Total) - The number of currently active requests, and the total number of requests made to the data sources since the server was started.
Work with the REQUESTS Page
Select one or more requests in the REQUESTS table with the respective check boxes and then perform the following actions on those requests:
• Clear Plan Caches button - Clears all query plan caches, in the event that current statistics gathering can have significantly changed information sufficient to change the query execution plan. Forces recalculation of all query plans at next time of execution which will be an initial performance hit.
• Purge Completed Requests button - Immediately removes all completed and failed requests. This is useful to reset the view prior to testing a set of requests.
• Cancel Requests button - Clears all requests.
The REQUESTS Table
The REQUESTS table displays these columns for each request:
ID - Unique request identifier.
Status - Can be any one of the following values:
Status | Indicates that the request... |
STARTED | Was created but not invoked or executed. |
READY | Data is ready for a client, but no client has read the data. |
RUNNING | Is currently executing. If a client were blocked on the request, then the status would be running. |
WAITING | Exists in a wait queue. |
COMPLETED | Execution successfully completed but is not yet closed. |
CLOSING | Is in the process of closing. |
SUCCESS | Successfully executed and has closed. |
FAILED | Execution failed. |
TERMINATED | Was closed by canceling. |
COMMITTED | Changes were committed to the database. |
ROLLED_BACK | Changes that might have been made were rolled back. |
TOP_TIME | Is in the group of requests that took the longest amount of time to complete. The number of requests in this group is configurable in Studio using this property: Number of Top Requests Tracked The default is 10 requests. |
TOP_MEMORY | Is in the group of requests that took the largest amount of managed memory. The number of requests in this group is controlled by the same property described for TOP_TIME above. |
Owner - User ID of the user who submitted the request.
Parent ID - Unique ID for the requests parent process.
Session ID - STUDIO, HTTP (Web service), INTERNAL, or client procedure.
Session Name - Name of the component that initiated this request.
Start Time - Date and time the request started to execute.
End Time - Date and time the request was completed. Blank if the request is unfinished.
Total Duration - Amount of time elapsed between Start Time and End Time.
Rows Affected - The number of rows affected by this request.
Max Used Memory - Maximum memory used by this request, blocks of 2MB are initially reserved and then if additional memory is required 2MB blocks are incrementally assigned.
Max Disk - The maximum amount of memory ever occupied by the request
Summary - The SQL statement or procedure made by this request.
Request Details
Every individual request has additional detailed information that might help in troubleshooting failed requests. To view the read-only details, click the Show Row Details button for the row.
In addition to the information presented in the REQUESTS table (and described in
The REQUESTS Table), these details are provided:
Request Type - Either SQL or Procedure.
Owner domain - Name of the domain to which this owner belongs.
Session Type - The type of session: STUDIO, HTTP (Web service), INTERNAL, or client procedure.
Transaction ID - Unique ID for the requests session.
Duration - Amount of time elapsed between Start Time and End Time.
Server Duration - Represents the actual time spent by the server processing this request. The difference between Server Duration and Total Duration is the overhead on the server.
Current Memory - Memory utilization of this request.
Current Disk - The amount of current memory occupied by the request.
Description - a more complete description of the summary.
Message - Displays an error message if the request caused an error.