Skip to main content

How to Migrate SQL Server (On-Prem) to Azure SQL Database offline using DMS tool

How to Migrate SQL Server (On-Prem) to Azure SQL Database offline using DMS tool.


Hello Friends, today we will learn how do we migrate a On premises SQL Server to PaaS model SQL  Azure database.
To achieve this, we need to follow few basic steps i.e. prerequisites.

Before you can migrate data from an on-premises SQL Server instance to a single database or pooled database in Azure SQL Database, you need to assess the SQL Server database for any blocking issues that might prevent migration. Using the Data Migration Assistant v3.3 or later.





1. Select the New (+) icon, and then select the Assessment project type.
2. Specify a project name, in the Source server type text box, select SQL Server, in the Target server type text box, select Azure SQL Database, and then select Create to create the project.
3. On the Select sources screen, in the Connect to a server dialog box, provide the connection details to your SQL Server, and then select Connect.
4. In the Add sources dialog box, select your database, select Add, and then select Start Assessment.

5. Select Under Migration Scope, select Schema only.
6. In the Data Migration Assistant, specify the source connection details for your SQL Server, select Connect, and then select your target database.


7. Click on Connect.
8. Select the objects that you want to migrate. By default, all objects are selected.
9. Select Generate SQL script to create the SQL scripts, and then review the scripts for any errors.
10. Select Deploy schema to deploy the schema to Azure SQL Database, and then after the schema is deployed, check the target server for any anomalies

You are almost done!

Now, you will need to create a SQL database in Azure portal.

Refer my another page to create a Sample SQL database:

Well, once SQL database created in Azure, 

1. In the Azure portal menu or on the Home page, select Create a resource. Search for and select Azure Database Migration Service.


2. Create a new Migration project.


Now, we are in final stage: 

1. Now, select the source, target details
2. Select the objects that you want to migrate into Azure or All objects
3. Specify a name for the migration activity.
4. Review the migration summary if the information selected right.
Run the migration and monitor the progress.
5. After the migration completes, select Download report to get a report listing the details associated with the migration process.
6. Verify the target database(s) on the target Azure SQL Database server

That's it. Sit back & relax!
Do follow my other topics & share with your friends. 


Comments

Post a Comment

Popular posts from this blog

Troubleshooting transient connection errors to Azure SQL Database

Troubleshooting transient connection errors to Azure SQL Database Dear friends, I'm Yogesh. At my work place, I have faced these type of issues at times.  Let us understand what is this transient error?  A transient error has an underlying cause that soon resolves itself. It causes occasionally is when the Azure system quickly shifts hardware resources to better load-balance various workloads. Most of these reconfiguration events finish in less than 60 seconds.  During this reconfiguration time span, you might have connectivity issues to SQL Database.  To handle them, implement retry logic in their code instead of surfacing them to users as application errors. If your client program uses ADO.NET, your program is told about the transient error by the throw of  SqlException . What is the solution? Can Retry logic works? When your program communicates with SQL Database through third-party middleware, ask the vendor whether the middle ware contains retry logic for tr
Post a Comment
Read more

Geo-Replication in SQL Azure Database

Geo-Replication in SQL Azure Database Geo-Replication  is one of the Azure SQL features which allows making 3 readable replicas to your database in same or different data centers. Geo-Replication option is available for all databases and service tiers in all region. If it is enabled, the application initiates to a secondary database. we will review how to set up Geo-Replication on Azure SQL databases. Geo-Replication is an Azure SQL database feature that allows you to create a readable secondary database in the same region or cross-region. We can failover to the secondary database in case of an outage for a long time on the primary database server. We can also use this feature to migrate a database from one server to another server in the same or cross region with minimal downtime. Geo-replication uses the Always-on feature to replicate committed transactions to the secondary database asynchronously. Select the database, Click on 'Geo Replication' in left hand
Post a Comment
Read more

DTU and eDTU in Azure SQL

DTU and eDTU in Azure SQL The performance of SQL Database is based on DTU. According to Microsoft, a DTU is a unit of measure of the resources that are guaranteed to be available to a single Azure SQL Database at a specific performance level within a single database tier. A DTU combines CPU, memory, data I/O, and transaction I/O. Databases can be placed into an  elastic pool  on a SQL Database server that shares a pool of resources among those databases. The shared pool of resources are measured by  elastic Database transition units (eDTU) . The advantages of an elastic pool are: They are scaled automatically. They provide predictable costs. They are widely used for  varying  and  unpredictable usage patterns . Determining DTUs for Workloads ·          If you are planning to move your on-premises Databases to Azure SQL Database, Azure provides a  DTU Calculator  to find the approximate DTUs required for setting up the database. ·         
1 comment
Read more