Why not parse the SOURCE database for prohibited T-SQL before spending hours exporting data that will never be written?

When using the Deploy database to Microsoft Azure SQL Database, the wizard spends, on my smallish database, 5 HOURS churning through data, writing the BacPac file, only at the end to go "Oops!  Sorry, that T-SQL construct isn't allowed." and closes the door on going any further.

This makes no sense to me!

All the T-SQL to deploy is already in the source database.

Parse it for invalid constructs.  Report prohibitions.  Stop.  Otherwise, with no prohibited syntax found, THEN export the millions of rows for the next several hours.

Please, Azure DB Team, consider re-sequencing the wizard's operations to save us all many elapsed, frustrating, hours of retrying deployments.

August 27th, 2015 8:04pm
Please raise your request under https://connect.microsoft.com/SQLServer to send the feedback directly to Microsoft Product teams.
Free Windows Admin Tool Kit Click here and download it now
August 28th, 2015 6:29am
https://connect.microsoft.com/SQLServer/feedback/details/1737976
August 31st, 2015 9:37pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics