Pre-requisites for Configuring an Azure SQL Database as eG Database

The key pre-requisites in this regard and how to fulfill them are detailed below:

1. At least one Azure SQL database should pre-exist on the Azure cloud. This is because, only an existing Azure SQL database can be set as the eG database. You cannot use the eG manager setup wizard to create a new SQL database on Azure for this purpose.

2. Determine the host name / IP address and port number of the SQL managed instance that should host the eG database. This is required because, when setting up the eG manager, you need to specify the Database Server Name / IP and the Database Server Port for the eG manager to communicate with. To figure this out, follow the steps detailed below:

   • Login to the Azure portal.

   • Type whole/part of the phrase, 'SQL databases', in the search text box. Once SQL databases appears in the search results, select it (see Figure 1).

     

     Figure 1 : Selecting the SQL databases option

   • From the list of databases that then appears, click on the Azure SQL database that you want to configure as the eG database (see Figure 2).

     

     Figure 2 : List of Azure SQL databases

   • In the page that appears next, click on the Connection strings option in the left panel.

   • Then, click on the JDBC tab page in the right panel (see Figure 15).

     

     Figure 3 : Determining the host name of the Azure SQL database

   • In Figure 3, check the connection string in the JDBC (SQL authentication) section. The text string that appears after jdbcsqlserver:// and before : (colon) in the connection string (as highlighted in Figure 12) is the host name of the managed instance. Specify this host name against Database Server Name/IP when configuring the eG manager's backend.

   • Likewise, make a note of the number that appears between the first and second : (colons) in the connection string (as highlighted by Figure 4). This should be specified as the Database port number when configuring the eG manager's backend.

     

     Figure 4 : Determining the port number of the Azure SQL database

3. Regardless of where the eG manager is installed (whether on-premises or on the cloud), you need to make sure that the firewall is configured to allow communication between the eG manager and the Azure SQL database. For that, do the following:

   • Login to the Azure portal.

   • Type whole/part of the phrase, 'SQL databases', in the search text box. Once SQL databases appears in the search results, select it (see Figure 1).

   • From the list of databases that then appears, click on the Azure SQL database that you want to configure as the eG database (see Figure 2).

   • Figure 5 will then appear. Click on the Set server firewall link in the right panel of Figure 5 to configure firewall policies for the Azure SQL database.

     

     Figure 5 : Clicking on the Set server firewall link

   • This will invoke Figure 6. In the right panel of Figure 6, you will find a list of security rules that pre-exist. To add a new rule, click on the Add link in the right panel.

     

     Figure 6 : Clicking on the Add link to add a new security rule

   • Figure 7 will then appear. In the Firewall rules section in the right panel of Figure 7, first provide a Rule name. Then, in the Start IPv4 address and End IPv4 address text boxes, specify the IP address of the eG manager that should communicate with the Azure SQL database. This rule will allow traffic between the eG manager and the Azure SQL database.

     

     Figure 7 : Configuring a new security rule

   • Finally, click the Save button to save the changes.

4. The eG manager requires a special database user account for storing measures in the eG database. To know the privileges that should be granted to this account and how to configure such an account, refer to the Pre-requisites for Configuring an eG Database on a Microsoft SQL Server topic.