Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Viewing and applying schema changes

Updated on May 11, 2022

Review the list of schema changes to determine whether to proceed with the import and either automatically apply the schema changes, or download a SQL DDL script that defines the changes and manually apply the DDL to the database.

Before you begin:
  • Before starting, you must complete this task: Setting advanced mode and reviewing the archive contents
  • To automatically upgrade the application schema, your access group must have the SchemaImport privilege and the dynamic system setting database/AutoDBSchemaChanges must be true. Otherwise, you can create a DDL file to apply manually.
Note: You see this screen only if your archive includes schema changes.
  1. Click the class name to review the schema changes.
    Note: The table names displayed here may be shortened to accommodate database vendor name-length limits.
  2. Optional: If you did not configure the system to automatically apply the DDL, or if there is an error in your DDL, you see the View/Download SQL DDL button. Create a DDL file for your database administrator to apply manually:
    1. Click View/Download SQL DDL to create a DDL file.
    2. Give the DDL file to your database administrator to apply to the database.
    3. Continue the import after the database administrator applies the DDL file.
  3. Click Next to continue the import.
What to do next: If there are errors in the schema changes, the system displays an error page. Click Total errors to display the log.

Tags

Pega Platform 8.6 System Administration

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us