Pre-requisites for Configuring an eG Database on an Azure SQL Database Instance

Before even commencing the configuration process of the eG manager using an Azure SQL managed instance, ensure that the following are in place:

1. Depending upon where your eG manager is installed, you should enable/disable the Public Endpoint capability for the managed instance. This capability allows an endpoint to connect to the Managed Instance from the Internet without using VPN. To elaborate, if an on-premises eG manager has to communicate with the Managed Instance on the cloud, then Public Endpoint has to be enabled. On the other hand, if the eG manager is also on the cloud, then Public Endpoint should be disabled.

   To enable/disable the Public Endpoint capability, do the following:

   • Login to the Azure portal.

   • Select SQL Managed Instances from the list of Azure services.

   • Pick the SQL managed instance that you want to use as the eG backend.

   • Then, from the list of options in the left panel, select Networking.

   • Figure 1 will then appear.

     

     Figure 1 : Enabling/disabling Public Endpoint

   • Toggle the Public endpoint (data) flag in the right panel of Figure 1 to enable/disable the public endpoint capability. For instance, select the Enable option to enable the capability - i.e., to enable an on-premises eG manager to communicate with the managed instance. Likewise, select the Disable option to disable the capability - i.e., to enable the eG manager on the cloud to communicate with the managed instance.

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

2. Regardless of where the eG manager is installed, you need to make sure that the firewall is configured to allow communication between the eG manager and the managed instance. For that, do the following:

   • Login to the Azure portal.

   • Select SQL Managed Instances from the list of Azure services.

   • Pick the SQL managed instance that you want to use as the eG backend.

   • Then, from the list of options in the left panel, select Overview. Figure 2 will then appear.

     

     Figure 2 : Clicking on the Set server firewall option

   • Click on Set server firewall option in the right panel of Figure 2 to configure the firewall. Then, use the Allow option in the page that follows to allow access from the eG manager's IP/host name to the managed instance.

   • Finally, click the Save button.

3. The Azure SQL managed instance should allow ‘unlimited’ concurrent connections

   Given below are the steps to be followed to fulfill this requirement:

   • Login to the Microsoft SQL server that you want to use as the eG backend, as an administrator. 
   • Open the Microsoft SQL Server Management Studio.

   • In the Object Explorer that appears next, right-click on the node that represents the SQL server you are logged into, and then select the Properties option from the shortcut menu that appears.

     

     Figure 3 : Selecting the Properties option from the server shortcut menu

   • The Server Properties dialog box will then appear. From the Select a page panel in the left, select the Connections page, as depicted by Figure 4. The right panel will then change to display many options.

     

     Figure 4 : Setting the maximum concurrent user connections

   • In the right panel, make sure that the Maximum concurrent user connections field is set to unlimited (0).
   • Then, click the OK button to save the settings and to close the dialog box.