This lab is about exporting the on-premises database as a bacpac file and storing the bacpac file in Windows Azure Storage as a blob.
See my previous post here: How to create a Windows Azure Storage Account as a prerequisite for this lab.
Exporting to Windows Azure Storage
Once you create the bacpac file, you can import into a Windows Azure SQL Virtual Machine Database.
In this hands-on lab, you will learn how to:
The following is required to complete this hands-on lab:
In order to execute the exercises in this hands-on lab you need to set up your environment.
This post is part of a set of posts that go together:
This hands-on lab includes the following exercises:
In this section, you will log into the Windows Azure Portal and create an Azure Virtual Machine using the Windows Azure Gallery.
This exercise is about creating a bacpac file and putting it in Windows Azure Storage. As you recall, in Exercise 1 we created a storage account for this very purpose.
Right mouse click on MVC4Sample. Choose Tasks | Export Data-tier Application. You will be given the opportunity to name both the bacpac file and the container name. Recall that the Bacpac file is a blob file in Windows Azure Storage.
Exporting the data tier from an on premises database
Select the radio button Save to Windows Azure. Next, click on the Connect button. You will be prompted with a list of storage account names. Select the storage account name you provided from Exercise 1. You will also have the opportunity to specify a container name. Click Next.
Specifying storage account name and account key
Click the Finish button. The bacpac file has now been successfully stored in Azure storage. confirming the correct export. Click Close to complete the export process.
Finishing the export
Click Close to complete the export process.
Confirming the correct export
You have now successfully exported the bacpac file to Windows Azure Storage. You are now able to leverage this blob or bacpac file and import into Windows Azure SQL VM. This will be described in a future post.
Doesn't work. Export of bacpac files from 2012 is pointless because the bacpac is not compatible with SQL Azure Database. When you try and deploy it to SQL Database you get hit with
"The service objective 'Business' specified is invalid. (Microsoft SQL Server, Error: 40804)"
and there is nothing you can do.