1. Latest Release Home
  2. Guides
  3. Concepts
  4. Tools
  5. References
  6. Integrations
  7. Data Apps (Blueprints)
  8. Data Governance
  9. Incorta Applications
    1. Build applications via the Builder Agent
    2. Publish an application
    3. Manage application databases
    4. Manage application secrets
    5. Manage application versions
    6. AppKit CLI
  10. Release Notes
  11. Incorta Premium
  12. Release Support Policy
  13. Release Model

Guides → Manage Application Databases

Context

This content applies to Incorta Cloud deployments only.

Each application has two separate PostgreSQL databases that Incorta creates and manages for you: one for development and one for production. The application stores everything it saves in these databases, including statuses, notes, approvals, and other user-entered data.

  • Each application's databases are isolated from every other application.
  • You do not need to provision or configure the databases.
  • The development and production databases hold different data. Test data that you enter while you build does not appear in the published application.
DatabaseUsed byCreated
DevelopmentThe development sandbox and previewsWhen you create the application
ProductionThe published application onlyThe first time you publish the application

View the application databases

  1. In the Application Editor, select More.
  2. In the navigation panel, select Database. The Database page lists the Development and Production databases, with the status and storage usage of each.
  3. To view the details of a database, select the database. To return to the list, select All databases.

Each database has two tabs: Overview and Settings.

Database overview

The Overview tab shows the following information:

SectionDescription
StorageThe storage that the database uses, out of its storage limit
TablesThe tables in the public schema, with the number of rows and the size of each table
Applied schemaProduction database only. The schema currently applied to the production database.

The Applied schema section contains the following details:

FieldDescription
PhaseThe status of the most recent schema change, for example, complete
Applied atThe date and time the schema was applied
VersionThe application version that the schema belongs to
SnapshotThe identifier of the applied schema snapshot

Database settings

The Settings tab of each database contains the following sections:

SectionDevelopmentProduction
Connection detailsThe connection URL of the development databaseThe connection URL of the production database
External accessThe development database connection URL to connect from outside IncortaThe production database connection URL to connect from outside Incorta. Production credentials are available only to the hosted published application.
StorageThe storage that the database uses, out of its storage limitThe storage that the database uses, out of its storage limit
CredentialsRotate the database passwordRotate the database password
Danger zoneReset the development databaseDelete the production database

Connection details

Hosted runtimes receive the database connection automatically as the DATABASE_URL environment variable, so you do not need to configure the connection in your application.

The Connection URL field shows the connection URL of the development database. The URL is hidden by default. To show the URL, select the eye icon. To copy the URL, select the copy icon.

Important

The connection URL contains the database credentials. If the URL is exposed, rotate the credentials.

External access

External access lets you connect to the development database from outside Incorta, for example, to run the application locally against its development data.

If external database access is not configured on your deployment, the External access section shows Unavailable. Hosted applications are not affected.

The production database never allows external access. Production credentials are available only to the hosted published application.

Rotate the database credentials

All editors of an application receive the same database credential. Removing an editor's access to the application does not revoke a credential that the editor already copied. To revoke access for everyone, rotate the credentials.

Rotate the credentials if a connection string has been exposed.

  1. Open the Development or Production database, and then select Settings.
  2. In the Credentials section, select Rotate credentials.

Running environments reconnect to the database automatically with the new credentials.

Reset the development database

Reset the development database when it no longer matches your code. A reset drops the development database and recreates it empty from the schema of the current version. The connection URL stays the same.

Important

A reset permanently deletes all development data. The production database is not affected.

  1. Open the Development database, and then select Settings.
  2. In the Danger zone section, enter the application name to confirm.
  3. Select Reset development database.

Delete the production database

Warning: Delete the production database

Deleting the production database permanently deletes the database and all of its data. You cannot undo this action.

  1. Open the Production database, and then select Settings.
  2. In the Danger zone section, enter the application name to confirm.
  3. Select Delete production database.

Additional considerations

  • Reverting to an earlier version: Reverting syncs the development database to that version's schema, which can drop columns and their data. The production database is not affected.
  • Database service unavailable: If the database service is unavailable when you create an application, Incorta still creates the application without a database.
Warning: Deleting an application

Deleting an application permanently deletes both of its databases and all data in them.