Installing the K2 Database in Microsoft Azure SQL

The K2 database may be hosted in Azure SQL Database, under the following conditions:

• The K2 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 K2.
• The K2 application servers that host the K2 server components (e.g. K2 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 K2 database on Azure SQL Database is only supported when the K2 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 K2 to connect to the K2 database in Azure SQL Database, using static SQL credentials (SQL username and password).
• When K2 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 K2 installer for the first time, a K2 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 K2 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.