Introduction & Overview
The course is part of these learning pathsSee 2 more
This course explores how to plan and implement data platform resources specifically with regards to Azure SQL offerings. In particular, we will explore the benefits and features of the SQL PaaS offerings along with billing models, service tiers, and high availability options. We'll also cover migration scenarios and provide a demo that migrates a sample database from an on-premise SQL Server to an Azure SQL managed instance using DMS.
If you have any feedback relating to this course, feel free to contact us at firstname.lastname@example.org.
- Get a general understanding of Azure SQL databases
- Learn how to deploy Azure SQL databases
- Understand business continuity and security tie in with SQL databases
- Learn how to scale, upgrade, and partition your databases
- Learn how to migrate a database from an on-premise SQL Server to an Azure SQL instance
- Anyone who wants to learn about Azure SQL Offerings
- Those preparing for Microsoft’s DP-300 exam
To get the most out of this course, you have should a general understanding of the fundamentals of Microsoft Azure. Experience using databases — especially SQL Server — would also be beneficial.
Let's now take a look at the various migration scenarios, what they involve, and what you need to know to transfer your data to an Azure-hosted database. At the moment, you can migrate your data from Oracle, RDS SQL, SQL Server, PostgreSQL, and RDS PostgreSQL, to most of the Azure SQL database services. Over time, the variety of source databases that can be automatically or easily migrated to Azure will expand. Visit the Microsoft website to keep abreast of the latest supported migration scenarios.
Now, I want to explore what's required for using the data migration service for different Azure SQL target platforms. Let's start with the requirements that are common to all scenarios. You'll need a connection to Azure, using either a site-to-site VPN or ExpressRoute, the third party provided high-speed connection to Azure. The following network ports must be open, 443, 53, 9354, 445, and 12000. Make sure TCP/IP protocol is enabled. By default, it is disabled for SQL express installations. Make sure your firewall will allow database engine access. If you are using a firewall appliance, you may need to allow DMS access to the source server.
Now looking at the requirements that are specific to migrating SQL Server to an Azure SQL Database, obviously, you'll need an Azure SQL Database instance up and running, along with the Data Migration Assistant version 3.3 or later. You will need to give the Data Migration Service access to your source SQL Server through your firewall if you have a default SQL Server installation that will be on port 1433.
On Azure, create a server-level firewall rule that will allow the Data Migration Service to access your target databases. You'll need to make sure that the credentials used to connect to the source SQL Server instance have Control Server permissions.
If you are migrating data to an SQL Managed Instance, you will need an Azure SQL Managed Instance provisioned and up and running. If you are running a firewall appliance, you may need to add rules that will allow the Database Migration Service access to your source database, as well as files via SMB port 445. You will also need to open your source firewall to SQL Server traffic that is typically on TCP port 1433.
Also, allow the SQL Browser Service excess to UDP port 1434. The login credential that the migration uses, must be a member of the sysadmin server role. You'll need a network share to back up the source database too, and you will need to make sure that the service account that the source SQL instance runs under, has write privileges on that network share.
On the Azure destination end, you'll need a blob container and the shared access signature URI for that container.
Course Introduction - Azure SQL Databases Overview - Deployment Options - ARM Templates Deployment - DEMO: Deploying Azure SQL Databases - Business Continuity - Security Database Services - Scale and Performance - DEMO: Scaling Azure SQL Databases - Partitioning Data - Migrating to Azure - DEMO: DMS Azure SQL Database Migration Process - Upgrade Scenarios - Summary
Hallam is a software architect with over 20 years experience across a wide range of industries. He began his software career as a Delphi/Interbase disciple but changed his allegiance to Microsoft with its deep and broad ecosystem. While Hallam has designed and crafted custom software utilizing web, mobile and desktop technologies, good quality reliable data is the key to a successful solution. The challenge of quickly turning data into useful information for digestion by humans and machines has led Hallam to specialize in database design and process automation. Showing customers how leverage new technology to change and improve their business processes is one of the key drivers keeping Hallam coming back to the keyboard.