Connect SQL form - Completing the Save tab

Enter an SQL statement to be executed by an activity that includes the RDB-Save method.

As a best practice, include only one SQL statement on this tab. If your situation requires multiple statements, place one statement each in separate Connect SQL rules. Your activity can cause the statements to be executed in the desired sequence. If your situation requires many statements executed in sequence, consider using a stored procedure. ( Pega Platform uses prepared statements and submits the SQL code in a single call to database software. Some database software versions may allow multiple statements in one call, but other software versions do not; use of multiple statements on this tab reduces portability and flexibility.)

Note: As an alternative, if your application needs to perform a simple operations against an external database, it is best practice to use the External Database Table Mapping wizard or the Connector and Metadata wizard or the to configure access to the rows as an external class. When such external access is configured for an external table, you can use the Obj-Open, Obj-Browse, and other Obj- methods to interact with that table through a class that represents it; you do not need to create SQL connector rules. However, you can still use the Save tab to enter the SQL statement that saves an instance to the database. See About generating connector rules and Data Model category — Database Class Mappings gadget.
Field Description
Save SQL Follow the guidelines in Data Mapping in SQL. Enter an SQL statement directly into the text box. You can use an INSERT statement, an UPDATE statement, or a CREATE statement on this tab.

For an INSERT statement, ensure that the property values that define the primary key have appropriate values (unless the primary key is computed, as through auto-increment.)

Some external database tables may include one or more auto-increment columns. Do not reference such columns in an INSERT statement or attempt to change values for these columns with an UPDATE statement.

Error Handler Flow Optional. Identify a flow rule that is to be started when this connector rule is started by a flow rule but fails when the Integrator shape throws a ConnectorException exception. The default flow rule Work-.ConnectionProblem provides one approach for handling such problems. See Handling connector exceptions.
Test Connectivity After you save this rule, you can click to confirm connectivity to the database. No database operations are performed. See More about Connect SQL rules.