Having worked with Azure SQL Database and its many flavours for couple of years now I am confident in building deploying, whether manual or templates. Being in Azure you can take the same mind set to build non-Microsoft database tech such as PostgreSQL, MySQL etc.
Let’s work though one, it’s that easy.
This post is to help you if you are suffering from the following issue:
A VSS writer has rejected an event with error. The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Consider the following scenario:
In this situation, you notice that the VSS backup fails and triggers the following entry in the Application log.
Do you enable this setting to allow automatic tuning to care of all your performance needs? Well not ALL your needs, more so:
SQL Server 2019 is ready available for use, but before you download you should review the webinars, white papers and eBook available on the technology (definitely the eBook 😉 ).
You can find the eBook at the following link –
https://info.microsoft.com/ww-landing-introducing-sql-server-2019-content.html
I think many have covered how you should backup your SQL Server database to Azure storage (also known as backup to URL) but what about restoring? Lets assume you have setup backups and they are working, this is what I usually do.
Would you like to troubleshoot a deadlock in Azure SQL Database? To do this you probably will be after the deadlock graph. So does this mean that you need to setup your own extended event session? No, it doesn’t.
In the previous blog post I did a quick overview building a SQL VM (imaged) in Azure. It is now time to clarify some backup techniques because it can get confusing.
At a high level there are 3 techniques.
I prefer not setting up manual backups to storage accounts, I have done it, I just find it painful to setup/support/fix. So my choice would be automated backup vs “Azure backup” for SQL VM. What’s the difference?
Let’s create a virtual machine in Azure that has an imaged copy of SQL Server on it. I want to do this because down the line I want to show how you can setup automated backups to a storage account based on an IaaS extension, when I do that I will most likely talk about the different backup options because there are many.
An amazing blog post by Microsoft describing the idea of hot patching the database engine in Azure SQL Database to allow for minimal downtime when applying patches to SQL Server. We know that it is one of the benefits of Azure SQL Database but now we get some insight into how it’s done.
Hopefully you know that SSMS is a separate install from the main SQL Server install. You can find the binaries from Microsoft (https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms) Using SSMS version 18.2, whilst playing around with the options I noticed a dark theme was available, easy to say I got a little excited, then I didn’t.
