This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a .bak file on my machine I am trying to restore into an azure database. I then created an Azure storage/blob account to hold this file, to restore via ssms but unfortunately, the file is large (about 35GB) and crashes my machine multiple times.
How can I get this file from my local machine to Azure SQL database? Suggestions, please
Thanks
An Azure relational database service.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 51%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDW%3C/text%3E%3C/svg%3E)
Sort of rediculous that MS wouldn't make a simple process for this... given that you would think they would WANT people migrating to the cloud, and this would be the simplest method for end users.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 37%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHL%3C/text%3E%3C/svg%3E)
It is ridiculous.
For trivial small databases, it's not a big deal, but for medium to large databases (i.e., those found in the real world) it makes Azure SQL Database a particularly difficult solution to implement, as well as it taking a huge amount of time.
With the amount of effort to work around this restriction, and the risks those steps introduce, I've never understood why. It's the biggest reason an Azure migration will fail.
Not sure why Amira suggested that you would take the route over the Azure VM. You can just as well run DMA directly against your local server. I think it is also possible to do the migration by BACPAC, but if the backup is 35 GB, the bacpac may be of similar size.
In any case, you cannot restore the backup to Azure SQL Database directly by any means.
Thank you both, passed step 1, I’m trying to restore the backup file from url via the sas token as VM route seem relatively costly. I understand the backup file can’t be restored to database directly. I’ll put into consideration the bacpac & DMA route. Keep you posted !
Kind Regards
Restoring a .bak file directly to an Azure SQL Database is not supported because Azure SQL Database is a managed database service that does not provide the same access to the underlying file system as SQL Server running on a VM or on-premises. Here is a workaround :
Thanks for your response Amira, the issue here is that I am stuck on step 1. The file upload to blob storage never completes and crashes my machine every time. That's why I need a workaround.