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.
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.”
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.
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.
Taking a screen shot from my Azure Portal, you will see the available hardware configurations available for Azure SQL Database.
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.
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.
There is a new (ish) interface to looking and configuring backups for your Azure SQL Database. This can be found within the settings section of the SQL Server.
As you can see, by default we have 7 days retention to allow for PITR – Point In Time Recovery, anything longer you will need to setup long term retention.
Following on from a previous blog post (https://blobeater.blog/2021/01/15/sql-server-linux/) on installing SQL Linux, a common requirement will be the need to connect to it to issue queries, typically via SQLCMD). There isn’t too much to it but still an important step.
If you are building database solutions in Azure , using Azure SQL Database then you will know that you have a purchasing option decision to make. That being should you use a vCore model or DTU approach?
