Configuring Microsoft SQL Server

Databases

Note: Unless otherwise specified in the dedicated requirements sections, these requirements are applicable to all Automation Suite products.

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 have the option to 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	ADO.NET
Orchestrator	AutomationSuite_Orchestrator	ADO.NET
Automation Hub	AutomationSuite_Automation_Hub	ADO.NET
Data Service	AutomationSuite_DataService	ADO.NET
Insights	AutomationSuite_Insights	ADO.NET
Test Manager	AutomationSuite_Test_Manager	ADO.NET
Task Mining	AutomationSuite_Task_Mining	ADO.NET
AI Center	AutomationSuite_AICenter	JDBC
Document Understanding	AutomationSuite_DU_Datamanager	ODBC

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.

SQL collation

Automation Suite supports SQL collation set to SQL_Latin1_General_CP1_CI_AS at both the server and database level. We strongly recommend this particular setup for optimum performance and stability.

While you have the flexibility to use a collation of your choice, be aware that untested configurations can potentially lead to unexpected issues.

Important:

We do not recommend using Binary SQL or any collations that are case-sensitive, as they cause known issues while installing Automation Suite.

Permissions

If you want the installer to create a database on the provided SQL server, make sure to grant at least the dbcreator role to the SQL account used to connect to the database.

If you want to create your own databases for all the products, you must grant the SQL account the db_owner and db_securityadmin roles for all Automation Suite databases.

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

Note: We only use the db_securityadmin and db_ddladmin roles during installation or if the databases are reprovisioned, so you may revoke these permission afterwards.

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

Note: Insights does not support Azure AD authentication. If you authenticate using Azure AD, dashboards cannot be loaded and data cannot be fetched from the Microsoft SQL database.

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

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

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 Data Service

Data Service requires SQL Server version 2016 or higher.

If you create your own database using SQL Server version 2019 or higher, make sure to grant the following Data Service permissions to your users:

GRANT ALTER ANY SENSITIVITY CLASSIFICATION TO {userName};
GRANT VIEW ANY SENSITIVITY CLASSIFICATION TO {userName};

SQL requirements for HA

For a high-availability configuration of your SQL Server, select an Always On availability group. For more info, refer to Overview of Always On availability groups.

SQL requirements for Orchestrator

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'

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 ON

If you use different databases for Test Automation and/or Update Server, READ_COMMITTED_SNAPSHOT must be enabled on those as well.