Maintain a Blue Prism database server

Click this icon on the toolbar to view and download a PDF version of this guide.

The instructions and recommendations contained within this section should be considered as a guide only. There are a large number of options available when maintaining databases that may relate not only to database specific settings, but also the host instance, as well as all instances on a given server.

It is recommended that both industry standard best practice and recommendations from an experienced database administrator are sought. These should be reviewed in light of the wider impact that they may have on the overall environment.

Customizing the database

When considering directly interacting with the database or its schema, it is essential that you are aware of the following limitations and advice.

Database modification

It is not supported to directly update databases created or provided for use with, or by, Blue Prism products. This includes adding, updating, modifying or deleting data; as well as making any changes to the database schema, including but not limited to adding new tables, changing table columns, changing indexes or foreign key constraints. Changes are only supported under instruction from Blue Prism Global Customer Support; or where provided in Blue Prism documentation and accompanied by a statement that endorses support when such changes are applies. The database schema, and the purpose and use of each column by Blue Prism is subject to change and should not be expected to remain consistent across Blue Prism versions.

Querying the database

It is not recommended to query the database manually or through use of third-party tools, however we recognize that there are some scenarios that may necessitate it; such as for reporting purposes. Where queries are run against the database(s), users are advised that it is their responsibility to:

  • Review the complexity, cost, and frequency of queries to ensure that they do not impact or impede the performance or behavior of the system.
  • Be aware of the queries and the frequencies and to proactively share the details with Global Customer Support when raising support tickets.
  • Disable these queries if required as part of troubleshooting or when issues are being investigated.
  • Permanently disable queries that are suspected of contributing or causing adverse behavior or performance.