Follow

Configure Discovery Hub® with Azure SQL Managed Instance

Overview

This guide will cover how to deploy and configure your environment using the Azure Marketplace App: Discovery Hub with SQL Managed Instance

The deployment of the Azure resources will vary depending on Azure resource availability. Deploying Azure SQL Database Managed Instance generally takes 3-6 hours. Configuring your Discovery Hub environment generally takes ~20 minutes.

Complete the following steps to configure Discovery Hub with Azure SQL Managed Instance:

  1. Deploy Discovery Hub and SQL Managed Instance
  2. Configure Accounts and Permissions
  3. Find the server name
  4. Connect to the virtual machine
  5. Configure the Discovery Hub Environment
    • Activate Discovery Hub
    • Configure the project repository
    • Add a Modern Data Warehouse
  6. Configure the ODX Server

1. Deploying Discovery Hub® with SQL Managed Instance

  1. Go to https://azuremarketplace.microsoft.com/en-us/marketplace/apps/timextender.timextender_dh_mi?tab=Overview
  2. If you are not signed in to your account, sign in now
  3. In the Azure Marketplace, perform a search for TimeXtender
  4. Select the deployment option from the search results.
  5. Scroll down and select Get it Now and then select Continue. You will be redirected to a page that contains a wizard for creating your resources.
  6. In Step 1 of the wizard, configure basic settings, and then click OK.

SQL_MI_Step_1.png

Setting

Description

Default Value

Requirements

Virtual Machine Name

The name of the virtual machine

Discoveryhub-vm

Must be between 3 and 79 characters long and contain letters, numbers and hyphens only.

Managed Instance Name

The name of the managed instance

dhmanagedinstance

Must be between 3 and 63 characters and contain lowercase letters, numbers, and hyphens only.

Analysis Services Name Prefix

Prefix for the Azure Analysis Services

discoveryhubas

A randomly generated suffix will be applied. Must be between 3 and 24 characters long (with suffix) and only contain lowercase letters.

Subscription

The subscription to place the resources in

 

 

Resource Group

The resources group that will contain all deployment items

 

Must be an empty resource group

Location

Location of the resource group

 

 

 

  1. In Step 2 of the wizard, configure the virtual machine’s resources and settings, and then click OK.

SQL_MI_Step_2.png

Setting

Description

Default Value

Requirements

Virtual machine password

Administrator username for the virtual machine

 

Cannot be the name “Administrator”

Administrator’s password

Password for the virtual machine administrator

 

The password must contain at least 12 characters, with at least 1 letter and 1 number

Confirm Password

 

 

Must contain at least 12 characters, with at least 1 letter and 1 number

Virtual Machine Size

Size of the virtual machine

Standard_DS2_V2 

 

Diagnostic storage account

Select an existing storage account or create a new one.

<virtual machine name>-randomly generated number

Must be unique

Public IP Address for the VM

Select an existing IP address or create a new one

<virtual machine name>-ip

 

DNS Prefix for the public IP Address

DNS prefix for the public IP address

<virtual machine name>-randomly generated number

Must be unique

Virtual Network

Select an existing virtual network or create a new one

VirtualNetwork

 

Virtual Network Address Space

Address space for the virtual network

10.0.0.0/16

See networking requirements below

Managed Instance Subnet name

Name of the subnet that will contain the managed instance

miSubnet

 

Managed Instance Subnet Address Prefix

 

 

See networking requirements below

Management Subnet Name

Name of the subnet for the managed instance subnet

managementSubnet

 

Management Subnet Address Prefix

Address range for the management subnet

10.0.1.0/24

See networking requirements below

 Networking Requirements

When designing the Managed Instance network, keep the following in mind:

  • When choosing an existing virtual network, Azure will “grey out” any network that does not satisfy the requirements.
  • The subnet that the Managed Instance is deployed to must be empty
  • If more instances, resources or connections are needed then adequate space is needed for them.
  • When deciding on the virtual network address space, keep in mind that Azure requires the following IP addresses for the Managed Instance subnet:
    • Five addresses for its own needs
    • Each General Purpose instance needs an additional 2 addresses
    • Each Business Critical instance needs an additional 4 addresses
  • The virtual network address space needs a minimum of 64 addresses (/26 prefix)
  • While Azure only requires a subnet size with a minimum of 16 IP addresses, we follow their recommendations and therefore require the managed instance to have at least a /27 prefix (32 addresses).
  • The management subnet has a minimum of a /29 prefix (8 address, 3 usable). Keep in mind that Azure reserves the first 3 possible addresses for its own use.
  1. In Step 3 of the Wizard, configure the managed instance resources and settings and click ok.

SQL_MI_Step_3.png

9. In Step 4 of the Wizard, confirm the summary settings by clicking OK.

10. In Step 5 of the wizard, review the terms of the agreements and click Create to initialize the deployment to the resource group you chose.

*Please note that deployment will vary depending on Azure resource availability. Select the Notifications icon at the top to view the status of your deployment

2. Configure Accounts and Permissions

Ensure the users, user groups, and service accounts have the necessary access and rights to the new server. Below are the required access and rights.

Accounts 

User Accounts 

Identify and/or create the following user accounts. Azure Active Directory (AAD), is recommended if using the Hybrid or Cloud configurations but the permissions are the same for local Active Directory (AD). If utilizing Azure Analysis Services then Azure Active Directory is required.  

  1. One user account for each Discovery Hub developer. 
  2. One Service Account must be created for each “non-development” environment. These will be used to run the Discovery Hub Multiple Environment and Scheduler Services. 

Security Group 

Create an Active Directory (AD) Security Group called TXDevelopers and add the developer user accounts. This will make it easier to apply permissions as developers work on and off the project. 

Application Server 

Local or Domain Administrator on the Application Server. This is required to be able to start and stop services. 

Database Permissions

Azure SQL Managed Instance 

The following permissions are needed when using Azure SQL Managed Instance: 

  • Data sources – db_datareader. 
  • Target databases – sysadmin or dbOwner. Note that if using dbOwner instead of sysAdmin, a user account with at least dbCreator rights must log in and create the project repository database from within the project repository settings dialog. 

3. Find the Server Names

1. Once your items have been deployed to your resource group, navigate to the resource group in Azure that contains all of the deployment items. This was assigned when configuring basic settings.

2. While viewing the Resource Group that contains all of your deployment items, find the SQL Managed Instance and click on it.

3. While viewing your managed instance, there will be a field called Host that contains your server name. Save this name somewhere safe because it will be needed for your configuring Discovery Hub®

MI_Host.png

4. Connect to the Virtual Machine

1. In order to activate and configure Discovery Hub, connect to the application server deployed on Azure. Navigate to the resource group in Azure that contains all of the deployment items. 

2. Locate the Virtual Machine in the resource group and click on it.

3. While viewing the page for the virtual machine, click Connect and download the RDP

4. Open the RDP file once it has downloaded and click Connect

5. Enter in the credentials to connect to the virtual machine that you created earlier and click Ok to connect.

Connect_to_VM.png

5. Configure the Discovery Hub® Environment

Activate Discovery Hub

1. Once you are connected to the Virtual Machine, start Discovery Hub; there will be an icon on the desktop for Discovery Hub that you can double-click to launch the program. The first time Discovery Hub is opened it will prompt you for an activation code. Select Activate over the Internet.

Activate_DH_1.png

2. If your server is located behind a proxy server you can add the credentials here, by activating the Use this Proxy server. If not, continue with the default value of Don’t use proxy server.

Activate_DH_2.png

3. On the following screen paste or type in your organization’s activation code and click This will synchronize with our licensing server and enable all your licensed features of Discovery Hub.

Activate_DH_3.png

Configure the Project Repository

1. After activating the software, you will receive a warning that the project repository settings are invalid. Click OK to dismiss the warning.

Configure_ODX_Server_1.png

2. In the Server Name field, enter the host name for the managed instance you created

3. Select SQL Server Authentication and enter the managed instance credentials.

4. In the Database field, type projectRepository and then click This will create your projectRepository where all of your project settings and metadata is stored.

Configure_ODX_Server_2.png

5. Click OK to close the window and return to Discovery Hub.

6. In the top-left corner, go to File and select New Project. Give your project a name and click OK to continue.

Adding a Modern Data Warehouse

1. Once you have created your project, right-click Data Warehouse, and then select Add Data Warehouse

Add_DW_1.png

2. In the Name field, type a name for the data warehouse. The name cannot exceed 15 characters in length

3. In the Server Name field, enter the host name for the managed instance you created.

4. In the Database field, type the name of a new database, and then click Create

5. Select SQL Server Authentication and enter the managed instance credentials that you created earlier.

Add_DW_2.png

6. Click OK to close the window and return to Discovery Hub.

6. Configuring the ODX Server

 

Please see the article, Configure and Manage the ODX Server, for configuring the ODX Server using SQL Server data storage.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.