You are interested in being even more awesome at your job than you already are.You know the basics of SQL Server backups and recovery models.You are an amazing and wonderful person.You already have a test SQL instance, SQL 2012, SP1, CU2 or higher.You already have an Azure account/subscription.

All of this in T-SQL, because the SSMS GUI is cumbersome.Restore that backup to a new database name.Backup the database to the new container.Create a new SQL Database on my 2016 instance.Create a storage account of Kind “Storage”.The credential is specified in a backup or restore statement. SQL Credential – created at the SQL instance – uses the access key to allow backups to go into containers.URL – the location specific to the container you have created.Access key – a code you need in order to access a Storage account.Container – a sub-group within a storage account – roughly similar to a folder on a fileshare.Storage account – loosely similar to a Fileshare…created to hold a specific type of items.Resource – anything in Azure you can create, such as SQL Databases, Virtual Machines, Storage accounts, etc.Resource Group – a logical container for grouping like-purpose resources.Subscription – an account to create and use Azure resources.We aren’t talking about AWS or Google today. Otherwise scroll on down for text and screenshots, with code samples: If you like to watch videos to learn new technology, I offer this. Also useful for veteran DBAs (like me) that suddenly have to sort out cloud technology. Those are all great topics that are very well documented elsewhere. It does not include discussions around backup types, recovery models, etc. This is an intro level post, specifically written for the new and accidental DBAs that have been told to direct their SQL Server backups to Azure storage…but without any additional information. My Pluralsight course for new SQL Server DBAs

Download sql backup master key