UiPath Automation Suite

The UiPath Automation Suite Guide

Configuring Microsoft SQL server


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. Refer to the following table for the names you need to use.

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

Product / serviceDefault database nameConnection string format
Shared Platform CapabilitiesAutomationSuite_PlatformADO.NET
Automation HubAutomationSuite_Automation_HubADO.NET
Data ServiceAutomationSuite_DataServiceADO.NET
Test ManagerAutomationSuite_Test_ManagerADO.NET
Task MiningAutomationSuite_Task_MiningADO.NET
AI CenterAutomationSuite_AICenterJDBC
Document UnderstandingAutomationSuite_DU_DatamanagerODBC



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 }.



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

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



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 role 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:

  • db_ddladmin1
  • db_datawriter
  • db_datareader
  • EXECUTE permission on dbo schema

1 The db_ddladmin role is only needed during installation or migration. For security reasons, we recommend that you remove it after installation or migration (using ALTER ROLE db_ddladmin DROP MEMBER [SQLReadWrite]), and add it back before upgrade (using ALTER ROLE db_ddladmin ADD MEMBER [SQLReadWrite]).


SQL requirement for Full-Text Search

Automation Hub and Document Understanding require 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 Automation Hub tenants and 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 objecservice 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 Data Service

Data Service requires SQL Server version 2016 or higher.
The collation sequence is the same as the default one: Latin1_General_CI_AS.

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:



Updated 5 months ago

Configuring Microsoft SQL server

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.