August 6, 2016 at 10:19 pm
Comments posted to this topic are about the item Backup Strategy in Azure SQL?
August 7, 2016 at 9:53 pm
Great write-up showing the use of the portal for backup. My largest lament with SQL Database in Azure is the lack of automation that I can control and schedule like we had with SQL Agent. While databases are automatically backed up in Azure, I might want to back one up on my schedule (my demo database has changed at this moment).
Hopefully MS recognizes the importance of this and will address it with something as easy to use as SQL Agent. Their runbook option or using ARM doesn't thrill me.
August 8, 2016 at 9:27 am
As the developer of something that does exactly this you may want to try it out - it schedules bacpac exports and imports that are made from temporary databases which are transactionally consistent. It also does Azure Blobs, Files, Tables backup too.
https://www.cherrysafe.com/[/url]
Programming Factotum
Red Gate Software Ltd
August 8, 2016 at 11:54 am
I agree. There is nothing easier than the SQL Agent. There are some alternatives, but they should invent the Azure SQL Agent.
August 9, 2016 at 8:36 am
The ability to restore over top of an existing db needs to be a feature to be added. It appears you can still only restore to a new name. Some applications are so complicated that switching all of the connections to a new db name just isn't an option.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply