Skip to content

Latest commit

 

History

History

managedinstance

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

README.md

DPi30 Managed Instance Deployment Template

This template is for data estates that need a place to consolidate their data into one place for reporting while having the full SQL Server feature set.

It will deploy:

  • SQL Managed Instance (Gen 5 4 Cores)
  • Azure Storage Account (Blob Storage)
  • Azure Data Factory
  • Jump Box Virtual Machine (B2ms with SSMS and Self Hosted Integration runtime preinstalled)

Getting Started

To deploy the DPi30 Simple Template click the button below and fill in the required information.

Next Steps

After deploying the simple template you will want to start getting data into your database. Here a few links to help you get started:

Rationale

Why are you deploying Azure SQL Managed Instance?

Managed Instance allows you to use SQL Server features such as cross database queries without having to worry about items like backups or setting up with best practices.

Why deploy a blob storage account instead of data lake?

SQL Azure Managed Instance currently cannot access Data Lake Gen 2 directly. To allow for bulk insert of data we are using Blob storage for direct access from SQL Azure.

Why did you deploy Data Factory?

Data Factory is the best option to orchestrate all this data movement and has the best options for moving data from one place to another quickly and easily.

Why did you deploy a Virtual Machine?

Since Managed Instance is contained within a Virtual Network the safest way to access it is via a Jumpbox sitting inside the same Virtual Network.

Why did you use a separate virtual network?

Because of the complexity of network routes and subnet requirements for Managed Instance it is easier to have it be in it's own vNet and then peer the network to your current vNet.