Skip to main content
LinkedIn
Copied!

Table of Contents

Running SQL queries on Pega Cloud

Version:

Only available versions of this content are shown in the dropdown

As a Pega Cloud client, to retrieve data from the internal PegaDATA or PegaRULES databases, you can run SELECT statements using Query Runner.

You can run queries against non-binay large objects (BLOB) columns in your database, view the results, and export the results to an Excel spreadsheet or .pdf file. A maximum of 500 rows are returned for each query.

Pega Cloud Services provides Query Runner, Query Inspector, and Schema Tools in Pega Platform for clients to manage their database. These database tools are not available to on-premises clients.
  1. In the header of Dev Studio, click Configure System Database Query Runner .

  2. Click the Query Entry tab.

  3. In the Choose your database field, select from the PegaRULES or PegaDATA databases that you want to run the query against.

  4. In the SQL query field, enter the query that you want to test. The query must contain the fully qualified name of the table.

  5. Click Run. Pega Platform displays the resulting SELECT SQL query in the RESULTS pane.

  • Viewing previously run queries

    You can view queries that were previously run on the History tab of the Query Runner landing page. Queries that are too long to display in the table are partially displayed followed by an ellipsis.

  • Exporting previously run query results

    You can export results from queries previously run in the Query Runner to an Excel or PDF format.

  • Using Query Inspector to improve SQL queries

    You can use Query Inspector to generate an EXPLAIN PLAN to help tune a SELECT SQL query for your internal Pega Platform databases on Pega Cloud.

  • Improving database batch processing performance

    You can improve bulk processing performance for database batch insert, update, and delete operations by using the database/batchUpdates setting in the prconfig.xml file or dynamic system settings. This setting lets you override the default batch size during a Commit operation for databases that support batch updates.

Related Content

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us