Creating the K2 database in the Azure SQL Database server

If you are using Azure SQL Database to host the K2 database, set up an empty Azure SQL Database before you run the K2 installer for the first time. This topic describes how to install the K2 database in the Azure SQL Database server.

At a high level, the sequence of steps is:

  1. Create an Azure SQL Database.
  2. Install the product and point to the Azure SQL database.

Considerations

  • All Azure services use the UTC time zone. If the K2 database exists in Azure SQL and your K2 server is in another time zone, it could result in a delay or failure of asynchronous workflow events. Examples of asynchronous events include:
    • Sub workflows
    • Escalations and Reminders
    • Start rules
    • Other rules or steps with a time-delay or time calculation aspect

    A workaround is to adjust the time zone of your server to match the Azure SQL time zone.
  • When installing the on a Virtual Machine (VM) hosted in Azure, in workgroup mode as opposed to domain-joined mode, you need to install using a local administrative user on the VM, not with the Azure user account
  • If the application server or K2 SQL Database is hosted in a cloud service, we highly recommend that the K2 database is installed in a SQL server where there is high bandwidth and low latency between the application server(s) and the database server. (For example, in Microsoft Azure the Application Server Virtual Machine and the SQL Database should be in the same subscription and geographical location.) Alternatively, when installing the K2 database in an Azure SQL database but the application server is in a different location, ensure that the network latency between the application server and the SQL server is as low as possible (for example by configuring Azure ExpressRoute or a dedicated network circuit). Excessive network latency between the application server and SQL server will negatively impact performance of your product environment.