CAST Engineering Dashboard - Information - How to identify and execute SQL query involved in data display
Purpose
This page provides you the information on how to identify the specific section a SQL Query belongs to, after the SQL Traces have been activated. It will provide the steps on how to adapt that query and execute on the pgAdmin manually.
Applicable in CAST Version
| Release | Yes/No |
|---|---|
| 8.3.x | ✅ |
| 8.2.x | ✅ |
| 8.1.x | ✅ |
| 8.0.x | ✅ |
| 7.3.x | ✅ |
Applicable RDBMS
| RDBMS | Yes/No |
|---|---|
| Oracle Server | ✅ |
| Microsoft SQL Server | ✅ |
| CSS2 | ✅ |
Details
Follow the below steps:
- Stop the web server
- Activate the SQL Traces in CED Dashboard, as explained in CAST Engineering Dashboard - Information - Configuring Dashboard to SQL trace
- Activate the traces on Retrievers in CED Dashboard, as explained in CAST Engineering Dashboard - Information - Configuring Dashboard to show the retriever name
- Restart the web server
- Log in CED
- Navigate to the desired page
- Open the stdout.log file present by default in the path - <Webservice_installation_folder>/logs/tomcatx-stdout.yyyy-MM-dd.log
- Identify the retriever that retreive the data from the schema. Remember that all the retrievers are named as per their purpose.
| Name of the RETRIEVER | Specific Section on Dashboard |
|---|---|
RETRIEVER_MODULE_FULLNAME | This retriever provides the module name |
| RETRIEVER_RULE_INVEST_VIOLATION_TABLE | This retriever provides the results of violations for quality rules |
| RETRIEVER_RULE_VALUE_TITLE | This retriever provides the metric description for a particular quality rule |
| RETRIEVER_MODULE_FAILED_CHECKS_COMPUTING | This retriever provides the number of failed checks |
| RETRIEVER_MODULE_TOTAL_CHECKS_COMPUTING | This retriever provides the number of total checks |
| RETRIEVER_MODULE_NB_OBJECT_VIOL_COMPUTING | This retriever provides the number of objects with violations |
For instance,
[05-17-2016 13:14:09][INFO]: [ROWREADER] Read: RETRIEVER_MODULE_FULLNAME
[05-17-2016 13:14:09][INFO]: [ROWREADER] Session Id : 0C09B1ABACD731DB0DEFE4A3713381C5
[05-17-2016 13:14:09][DETAIL]: [SQL] PREPARE Select o.OBJECT_FULL_NAME from test_73_shell_central.DSS_OBJECTS o where o.OBJECT_ID = 4
[05-17-2016 13:14:09][DETAIL]: [SQL] EXECUTE
[05-17-2016 13:14:09][DETAIL]: [SQL] Query Time < 1 ms
Identify the SQL query provided in the retriever in the [DETAIL]: [SQL]. In the above example, it is PREPARE Select o.OBJECT_FULL_NAME from test_73_shell_central.DSS_OBJECTS o where o.OBJECT_ID = 4
Execute this SQL query in pgAdmin manually, without SQL PREPARE statement. In the above example, run
Select o.OBJECT_FULL_NAME from test_73_shell_central.DSS_OBJECTS o where o.OBJECT_ID = 4
It will provide the results as below:
**Query Result**
"Shell full content"
**Notes/comments**
**Related Pages**