Installing the Database in Microsoft Azure SQL
The database may be hosted in Azure SQL Database, under the following conditions:
- The installer blocks installations if your SQL Azure databases are not on the minimum requirement. See the Compatibility and Support Matrix for the minimum supported version.
- When creating the new database, specify a setting of at least 10GB for the initial database size. You may need additional capacity, depending on your intended use of the product.
- The application servers that host the server components (e.g. Nintex Automation service, web sites etc.) are Virtual Machines hosted in Azure
- The machines are joined to your domain as if they were on-premises servers, or are installed in workgroup-only mode
- Due to latency considerations, hosting the database on Azure SQL Database is only supported when the application servers are Azure virtual machines that are hosted in the same Azure Subscription and Location as the Azure SQL Database.
- It is recommended to have two load-balanced Virtual Machines in Azure for high availability (see Azure documentation for supported Load Balancing approaches for Azure-hosted virtual machines).
- SQL authentication is used to allow the product to connect to the database in Azure SQL Database, using static SQL credentials (SQL username and password).
- When the product uses .NET 4.6.1 to establish the connection to the SQL server, by default the connection is encrypted using SS1 TD.
- Before running the installer for the first time, a database must be created in Azure SQL Database, and then populated using a DAC Package. Once the DAC package deployment is complete, you can run the Setup Manager and point it to this "shell" database; further database configuration will be performed by the Setup Manager. See the topic Creating the K2 database in the Azure SQL Database server for detailed information on this procedure.
* You cannot upgrade from 4.7 to 5.3 if you have 4.7 installed on-premises with the K2 database in Azure SQL. In this case, you must first upgrade your 4.7 installation to Nintex K2 Five (5.0) and then upgrade again to Nintex K2 Five (5.1), and then upgrade again to Nintex K2 Five (5.2), and then upgrade again to Nintex K2 Five (5.3), and finally upgrade to Nintex Automation (5.7).