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.”
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.