Automation Suite
2021.10
false
Banner background image
Automation Suite Installation Guide
Last updated 25. März 2024

Configuring Microsoft SQL Server

Databases

Each product in Automation Suite requires its own SQL database with corresponding specifications.

By default, the installer creates all the databases for you during the installation process. You must provide the necessary permissions for the installer to do so on your SQL server.

Alternatively, you can create your own databases. If you choose to bring your own databases for a new Automation Suite installation, we strongly recommend setting up new databases rather than using existing ones. This precaution is necessary to prevent any conflicts with the operation of Automation Suite that might occur due to leftover metadata from old databases.

The following table lists out the database names and their corresponding format.

Product / service

Default database name

Connection string format

Shared Platform Capabilities

AutomationSuite_Platform

Orchestrator

AutomationSuite_Orchestrator

Automation Hub

AutomationSuite_Automation_Hub

Insights

AutomationSuite_Insights

Test Manager

AutomationSuite_Test_Manager

Task Mining

AutomationSuite_Task_Mining

AI Center

AutomationSuite_AICenter

Document Understanding

AutomationSuite_DU_Datamanager

Important:

If you manually set the connection strings in the configuration file, you can escape SQL, JDBC, or ODBC passwords as follows:

  • for SQL: add ' at the beginning and end of the password, and double any other '.
  • for JDBC/ODBC: add { at the beginning of the password and } at the end, and double any other }.
Note:

You could use the databases in an elastic pool for better cost-effectiveness.

In the case of Apps, you cannot bring your own MongoDB.

Permissions

If you want the installer to create a database on the provided SQL server, then make sure to grant at least dbcreator role to the SQL account used to connect to the database.
If you wish to create your own databases for all the products, then the SQL account should be granted the db_owner and db_securityadmin roles for all Automation Suite databases. We only use the db_securityadmin role during installation or if the databases are reprovisioned, so you may revoke that permission afterwards.
If security restrictions do not allow the use of db_owner, then the SQL account should have the following roles and permissions on all databases (the only exception is Insights which still requires db_owner).
  • db_securityadmin
  • db_ddladmin
  • db_datawriter
  • db_datareader
  • EXECUTE permission on dbo schema

SQL requirements for Full-Text Search

Document Understanding requires the SQL Server to have the Full-Text Search component of the SQL Server Database Engine, which is not always installed by default.

If you did not select Full-Text Search when you installed SQL Server, run SQL Server Setup again to add it before configuring Document Understanding.

For more info, check this guide on how to add/install features on SQL server. You can also check here all the components that can be added to the SQL Server, which includes also Full-Text Search.

SQL requirements for Insights

Insights requires SQL Server 2019, including support for columnstore index and .json functions.

For Azure SQL, ensure the database is S3 service objective or above.

Make sure the compatibility level for Insights database is set to 130 or higher. In most cases, the default settings meet this requirement. For more info, refer to View or Change the Compatibility level of a Database - SQL Server.

The installation validates both conditions and alerts you if minimum requirements are not met.

SQL requirements for Orchestrator

For comprehensive details, see the SQL Server configuration section in the Orchestrator guide.

Important: To increase performance, avoid deadlocks, and prevent dirty reads in SQL, make sure that the READ_COMMITTED_SNAPSHOT option is set to ON.
Use this query to check if READ_COMMITTED_SNAPSHOT is enabled or disabled:
SELECT is_read_committed_snapshot_on FROM sys.databases
   WHERE name= 'UiPath'SELECT is_read_committed_snapshot_on FROM sys.databases
   WHERE name= 'UiPath'
If it is enabled, the returned value will be 1.
If it is disabled, the returned value will be 0. Use this query to enable it:
ALTER DATABASE UiPath
SET READ_COMMITTED_SNAPSHOT ONALTER DATABASE UiPath
SET READ_COMMITTED_SNAPSHOT ON
If you use different databases for Test Automation and/or Update Server, READ_COMMITTED_SNAPSHOT must be enabled on those as well.

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2024 UiPath. All rights reserved.