Udostępnij za pośrednictwem

Database Deployment Wizard in SQL Server 2014

  • Artykuł

In SQL Server 2014, we have a new wizard called Database deployment using which we can deploy a database which is in-premise to Azure without even having a knowledge of what Azure is all about. All what you require an Azure subscription to play with. I was playing with Azure and database deployment wizard and it was always failing with the below message in the log file :

Jan 8 2014 07:28:14 [Informational] Submit Job:ab0ffb0f-eb45-44eb-9e96-6aed7d997e68: Storage Account: portalvhdswvyp0s4s4nd1c.

Jan 8 2014 07:28:20 [Informational] Task:c2510211-1a61-4049-a73b-6e23596a43e0:Validation: Skipped: 100%: Successful: Validation Completed

Jan 8 2014 07:28:20 [Informational] Task:c2510211-1a61-4049-a73b-6e23596a43e0:Validation: Skipped: 100%: Successful: Task processing completed.

Jan 8 2014 07:28:25 [Informational] Task:115ef46b-28c5-474a-9d57-f55f8b3d9747:Provisioning: Stopped: 100%: Successful: Provisioning Completed.

Jan 8 2014 07:28:30 [Error] Task:fb8c34ea-b515-4589-91eb-4d0493247b33:Backup: Stopped: 0%: Failed: System.Data.SqlClient.SqlError: Cannot open backup device 'C:\Users\ggaurav\Desktop\cloud\db_backup_0ksax3ht.cvn.bak'. Operating system error 5(Access is denied.).

Jan 8 2014 07:28:30 [Error] Job:ab0ffb0f-eb45-44eb-9e96-6aed7d997e68: Running: System.Data.SqlClient.SqlError: Cannot open backup device 'C:\Users\ggaurav\Desktop\cloud\db_backup_0ksax3ht.cvn.bak'. Operating system error 5(Access is denied.).: Failed

The error message clearly states that we are not able to access the file on the local disk. The catch here is that, when we are trying to move the DB to Azure IaaS VM or to the SQL DB, it creates a temporary file, the location of which we give while entering the initial information in the wizard. If you look at the message, I've given the location on desktop, and in 99% of the cases, when you give the location on the desktop, it would fail. So the best option is to have the file stored in a folder which is not on desktop or give permission to the account explicitly and it would resolve the issue.

Happy learning & troubleshooting.

Comments

  • Anonymous
    February 10, 2014
    Have you filed a bug for this one. This  backup operation is done by SMO backup layer. The operation is not really failing because of the wizard, but because it is possibly SMO has issue with the path you provided. You provided a good clue regarding desktop path. I will log a bug for this item and hopefully get it resolved in the next available version.