SQL Server requisites

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio > Bizagi Studio installation > Bizagi Studio Server Installer > Bizagi Studio server system requirements > Database requisites >

SQL Server requisites


Bizagi Studio requires a database server for your processes repository.

Microsoft SQL Server is supported as the database server, as described below.


Supported versions and editions

The following are supported:




SQL Server 2019

Ensure you meet the SQL Server system requirements.

15.0.2000 or above

SQL Server 2017


SQL Server 2016, service pack 2

13.0.5026 or above

SQL Server 2016, service pack 1

13.0.4001 or above

SQL Server 2014

12.0.2000 or above

SQL Server 2012

11.0.2100 or above


For Bizagi Studio, all editions are supported.



If you use the SQL express edition, the maximum limit of a database is 10 GB. For further information click here.


Note that for a production environment (Automation Server), and due to its nature of demanding higher transaction processing or robustness, editions supported are Standard or higher.



The database instance must be set up with a collation which:

Is case-insensitive (CI).

Is not a Turkish collation.


Required configuration

The configuration of a SQL Server instance in order to work with Bizagi, requires the following:


SQL Server authentication

You will need to make sure SQL Server authentication mode is enabled for your database instance.


TCP/IP protocol

You will need to make sure TCP/IP protocol is enabled for your instance, as well as checking for recommended settings such as: an explicit TCP/IP port (instead of using dynamic ports) and allowing remote connections when needed.


Authorized login accounts

You will need at least 1 authorized login account using SQL Server authentication and having the required rights.



If you chose the Quick start option to have Bizagi Studio install a local SQL Server instance, then you do not need any additional configuration.

You may use the sa login included by default in that local instance.

The initial password for the sa login is BizagiBPM123


In case you do not want to use the sa login, then for the development (authoring) environment accessed by Bizagi Studio you may create and user additional login accounts. For more information on this, refer to Advanced configuration of SQL Server login accounts.


Verifying SQL Server configuration

Carry out the steps described next, to make sure that your SQL Server instance is set to work with Bizagi.


Before you start

To verify the configuration of your SQL Server instance (or set it up), you will need the SQL Server client and configuration tools.

What tools required for these steps are: SQL Server Management Studio and SQL Server Configuration Manager.


Both tools can be included when installing the SQL Server database. In case that your SQL Server version does not include the SQL Server Management Studio, you may download and install it directly from Microsoft's official web site at no cost.


Which version do I have?

To easily determine your version of SQL Server, use the SQL Server Management Console.

Run the following while connected to your database instance:

Select @@version




This shows you information about your instance, presented as shown:

The product's official name and service pack

The exact version number and its date

Additional detail about the SQL Server edition and bit support.




Checking the required configuration

Check or configure the following requirements.


1. SQL Server authentication

Run the SQL Server Management Studio.

Connect to your instance, and right-click it to select that instance's properties:




In the Security option, make sure that the SQL Server and Windows Authentication Mode is checked and then click OK.




2. TCP/IP protocol

Run the SQL Server Configuration Manager.




Enable the TCP/IP protocol for your database connection by locating the specific database instance (under the SQL Server Network Configuration), and right-click on this protocol to select Enable:




For the TCP/IP properties, it is recommended that the TCP port is explicitly defined (by default as 1433), so that dynamic ports are not used by the instance:





You may want to make sure that the SQL Server Browser service is in a started mode as well:





Changing these settings may require restarting your database service.

The TCP/IP port configuration requires that there is no firewall rule or corporate security software blocking that port used for your database connection.


For remote connections, make sure you configure the Allow remote connections property.

This property can be reviewed or activated through the SQL Server Management Studio, and in the database instance's properties.

Under the Connections option, make sure that this property is marked:




3. Authorized login accounts

Run SQL Server Management Studio and make sure you are connected to your instance with an administrator account (i.e, with the sa default one).


With this user, make sure you verify that the login account you will use for Bizagi Studio meets the following conditions:


The login account uses SQL Server authentication mode:




Make sure it has the sysadmin server role:




Verify that the login account is enabled and granted connection, at the Status options:




Updating a project

When you are updating a project additional from the access rights mentioned in the previous section, you need the following:


Server privileges

Set the user with privileges to backup and create the database





Open the Securables section, select the Effective tab and make sure that you have the following permissions;