Hi,
This is my third and last post dedicated to HADR solutions in Azure SQL Database, where I’ll introduce “Auto-failover groups“.
You can find the previous ones here:
So, first of all, what is Auto-failover groups?
Hi,
This is the second of three posts dedicated to HADR solutions in Azure SQL Database. In HADR in Azure SQL Database (Part I) I presented the “Scale out read-only Database” feature. In this one, I’ll talk about Active Geo-Replication and in HADR in Azure SQL Database (Part III), I’ll introduce “Auto-failover groups”.
So, first of all, what is Active Geo-Replication?
Hi,
AlwaysOn Availability Groups (AG) has been around since SQL Server 2012 and today it is widely used in HADR solutions. It also gives us the ability to have readable secondary replicas, allowing read-only access to the respective secondary databases. If you have read-intensive workloads (like reporting, ETL applications, etc.) you can have a significant performance benefit by simply directing those workloads to the secondary replicas.
In this post I’m assuming that you’re already familiar with this “old” feature so I’m not going to elaborate about it.
The thing is that AG is not present in Azure SQL Database (PaaS), so my purpose here is to show how to implement an HADR solution in Azure SQL Database, since we can’t use our well known (and beloved) AG and you’ll see that it’s actually pretty easy 😊
Hi there!
In SQL Server, many automated tasks are implemented via SQL Server Agent jobs. If you’re used to it, you may get a bit sad when you learn that SQL Server Agent is not present in Azure SQL Database. However if those automated tasks rely on T-SQL then they can still be easily implemented in Azure SQL Databases using elastic jobs that provide the ability to run T-SQL scripts on a schedule or on-demand 🙂
In this post I’ll create an elastic job from scratch to implement a table cleanup automated task for an Azure SQL database.
Continue reading “How to create Jobs in Azure SQL Database step-by-step”
Hi there!
In this post I’m going to show a very simple way to migrate a database between two SQL Server managed Instances in Azure. I’m not a big fan of bacpac files (although I work with it when necessary) so I’ll use a different approach here. Besides, when creating a bacpac file using SSMS there are some schema validations that occur at the beginning that will abort the bacpac generation for example if the database holds three-part names inside stored procedures. While not supported in SQL Azure DB it is supported in SQL Managed Instances (as are cross-database queries), and it can be quite frustrating to experience this show stopper when using bacpac’s to migrate or copy databases between Managed Instances.
Continue reading “How to migrate a database between two SQL Managed Instances in Azure”
SQL Land 