Last week we introduced breakthrough visualization experiences for the business continuity capabilities in Azure SQL Database. Setting up and administering your geo-replication is easier and more intuitive than ever before.
Posts By: Tony Petrossian
Previously, Auditing was introduced in the new Azure preview portal. Now, you can manage Auditing from the Azure portal and via PowerShell commands.
In this final post in our series on Business Continuity I’m going to look at point-in-time restore, a self-service feature available for Basic, Standard, and Premium databases.
This post continues our series on the Business Continuity/Disaster Recovery (BCDR) capabilities of Azure SQL Database and focuses on geo-restore. In my previous post on standard geo-replication I discussed how the various business continuity features map to service tiers.
This post describes some simple steps and guidelines on the process of using the information from this DMV to evaluate and pick the right performance tier for your database workload.
In this post, we will continue the conversation about the business continuity scenarios and discuss the newly released Standard Geo-Replication feature of Azure SQL Database. Before diving into the details, it would be useful to summarize the full range of the business continuity features now available in preview and discuss what you should use and why.
Auditing feature is now available for Azure SQL DB, in a preview offering. This is a key security enhancement that removes barriers from businesses wanting to manage their databases in the cloud.