Links may not function; however, this content may be relevant to outdated versions of the product.
Troubleshooting database requests
The Pega Platform database performance is a major factor in overall system performance, affecting response time for interactive, browser-based users, turnaround time for services, and throughput. You can use tools provided by Pega Platform to help you debug, trace, and analyze requests from the server to the Pega Platform database.
You can do the following:
- Use the Clipboard tool to view the
pyReportContentPagepage. It shows the pxSQLStatementPre and pxSQLStatementPost properties that contain the SQL statement that ran. These values are available after your run a report definition rule. The pxResultCount property shows the number of rows returned. Use the Clipboard tool to view these values.
- Use the Detail window of the Performance tool to view statistics for each user interaction since sign-on. For example, you can see the elapsed time (in seconds) that this user spent retrieving non-rule-resolved instances from the database.
- Use the Database Trace facility, accessed from the Performance tool Summary display, to create a trace of all database requests from your session.
- Generate a complete trace of all database requests by enabling the
database/dumpStatsentry in the prconfig.xml file or dynamic system settings.
- Use the Alert log to can find those database operations that required an unusually long time to process.
- Starting a database trace
The Database Trace tool produces a text file containing the SQL statements, rule cache hit statistics, timings, and other data that reflect your requestor session's interactions with the Pega Platform database or other relational databases. You can select the database options that are traced. Familiarity with SQL is required to interpret the output.
- Preventing truncated property values
When data values to commit to the database contain more characters than the corresponding column width in the database table, they are truncated when the object is committed to the database table. The system puts a warning message in the Pega log, truncates the data to the column width minus 1, adds a plus sign (+) to the end of the value, and saves the revised data.
- Debugging database schemas
By default, Pega Platform displays extensive details about SQL operations on the Pega Platform database that fail. This information is used for debugging.
- Running SQL queries on Pega Cloud
As a Pega Cloud client, to retrieve data from the internal PegaDATA or PegaRULES databases, you can run SELECT statements using Query Runner.
Previous topic Counting the rows in a database table Next topic Starting a database trace