On the theme of failover groups let’s do a quick recap on my environment. As shown below you can see the secondary database server called spacesql in West Europe.
Azure SQL Database – Secondary Database and Tiers
1
Category Archives: Azure
Azure SQL Database – Cancel Scale Up Request
You have an Azure SQL Database, it could be a single database, it could be a primary database within a failover group. Regardless of the context, what would you do if you need to upgrade the compute tier for the database but then you decide you no longer want to do this and want to immediately cancel it? In the past people just let the system carry out the task then once complete, rollback.
Azure SQL Database Restore to different server
It is quite a common requirement to restore a copy of a database to the same Azure SQL server, you just issue a COPY OF command. What if you need to restore a copy to a different target Azure SQL server? Well its similar, just with a slight difference in that you need to refer back to the source server within your code.
Snowflake in Azure
Being aligned to a global cloud like Microsoft Azure you have choices. Whether that is Azure SQL Database or Azure Database for MySQL for your relational database, it does not matter that is down to you are your design choices. The point here is that Azure has variations and flexibility with so many choices and this is no different within the “Big Data” analytics space.
Error creating Azure SQL Database
A quick post today, quite simply, the error message is:
“code”: “ConflictingDatabaseOperation”, “message”: “Operation on server x and database y is in progress. Please wait a few minutes before trying again.”
Azure SQL – Saving Costs
When moving to a cloud model for your database stack no doubt you will be involved in a costing exercise. The good news is if you have Software Assurance with your existing licenses then expect some cost savings when moving to the cloud. You can save up to 70% cost when compared to a pay as you go model.
Azure SQL Database – Contained user Model
I always follow a contained user model when setting up users within my Azure SQL Database. I do this so the user in question has access to only specific database(s) and does not have a login to the server. It becomes even more apparent the importance of this when you design a solution based on failover groups.
When a failover occurs to the secondary, I want a pleasant experience for the user. With the contained user model, the user goes with the database. I don’t want to do admin work on the new primary (post failover). Let’s see.
Azure SQL Database F and M series
Taking a screen shot from my Azure Portal, you will see the available hardware configurations available for Azure SQL Database.
Azure SQL Database Gen4 to Gen 5
For the past year Microsoft have said that Generation 4 hardware is soon coming to its end of life. I know many installations that have used Generation 4 over 5 so its time to think of the plan to facilitate this move.
Azure SQL DB – Troubleshooting CPU issues
When you have the need to find out real time what is causing high CPU issues within your Azure SQL Database, there is nothing better than using TSQL and SSMS. Azure portal will highlight the below, this is when I made CPU contention.
