This is the third and the final part of the series. We started with learning to register MS Azure and create SQL database & objects. Progressed to migrating the on-premise database to MS Azure using Export Data-tier Application. Now in the last installment, we’ll learn to migrate the on-premise database to Azure using Deploy Database to Windows Azure SQL Database wizard.
The primary difference between the two methods of migrating the on-premise database to MS Azure is that the ‘Deploy’ option requires an existing database server in Azure to which the on-premise database is directly deployed. The database is exported to a file, which is then directly loaded on to an Azure Blob Storage account.
However, both the methods of migration require an Azure Blob Storage account with a container and an Azure SQL server.
Prerequisites for Migration of DB
Before migrating the database on to MS Azure, ensure you have the following:
- An Azure subscription.
- ‘Azure Ready’ database; i.e., the database you want to migrate to Azure must be compatible.
Migration via Wizard
- Right-click the database and select Deploy Database to Windows Azure SQL Database as shown in the following figure.
- It will open Deploy Database Wizard as depicted in the following figure.
- The server information for the Azure SQL Database server is shown in the following figure. The BACPAC file is created locally and applied on the Azure SQL Server. It, therefore, requires you to store the BACPAC file in a temporary place on the server.
- Review the settings as shown in the following figure and click the Finish button.
- Wait for the process to complete as shown in the following two figures. At this stage, the wizard will validate the database, create the BACPAC file and apply the Azure SQL Server to create the database.
- After the process is completed, click the Close button. Connect to the Azure portal and you will see the migrated database in the list as highlighted in the following figure.
Migrating the on-premise database to MS Azure via Wizard is highly preferred for its simplicity. We hope this method of migrating the database gives you another reason to ponder over MS Azure. Implement this method to migrate your data to MS Azure and let us know your experience in the comments below.
With that, we finish our trilogy of Working with SQL Server Database on Microsoft Azure.
Will catch up in the next blog. Until then, Happy Learning!
- Working with SQL Server Database on Microsoft Azure (Part 2)
The huge volume of data generated around us, today, requires optimum storage and management to have any benefit for organizations. With a host of advantages that MS Azure possesses, especially…
- Working with SQL Server Database on Microsoft Azure (Part 1)
One of the trickiest implementation for any organization is the database. They require dedicated server and someone to manage it. Cloud services such as Microsoft Azure give organizations opportunity to…
- SQL Server – Reporting Services Migration
A while back, I got a task in my project, which was to migrate SQL Server Reporting Services from SQL 2008 to SQL 2012. Now, I had two ways of…
- Understanding Oracle Multitenant 12c database
Overview of Oracle Multitenant Databases Overview Database 12c Enterprise Edition introduces Multitenant, a new design that empowers clients to effortlessly merge numerous databases, without changing their applications. This new design…
- Different Application of Joins in SQL
Structurally organized with large quantities of information, databases are the backbone of every organization. That is why companies invest in database applications such as MySQL, PostgreSQL, Microsoft SQL Server and…
- SQL Server 2017 on Ubuntu Platform
Unlike previous releases of SQL Server, this time Microsoft has also given us the choice of picking the operating system on which we wish to install the application. This means…