Developers and testers all know the logistical nightmare of keeping multiple database backups around for the many scenarios needing testing. With the ability to backup to Azure Blobs, developers and testers now have a simple tool with which to enable backup/restore scenarios with little or no space constraints and rapid restore capability into Azure IaaS environments.
- [Narrator] As a developer, one of my most common frustrations is being able to get a fresh copy of production data. If you've ever had that problem, this feature will be very handy. You can ask your database administrators to back up to blog. Meaning, quite literally, that you can take a Sequel Server and back up a database directly into Azure from where you can then restore it into your DevDesk and other environments. Let me create the necessary container here in my Azure subscription. Click on the Plus sign; Storage; Storage account.
So this will be our destination for our backup. So we'll create a new storage account; leave all the defaults; General Purpose; Standard; Locally-redundant. And whenever this is meant for long-term backups, do not enable encryption, create a new resource group, and in my case the Sequel Server is in the West U.S. So the closest data center will make for the fastest backup. Now, the storage account is going to be our destination, and once deployed, we'll create a container within the storage account.
So when we back up from Sequel Server, instead of backing up to a file on a local server or an intake share, we will point Sequel Server directly to the Azure storage. The backup will run over HGPS, and you can also schedule your backup to run on a regular basis. If, for example, you need to refresh test data on a daily basis, well you can schedule. With deployment completed, we will click on Blogs, and go and create the blog container, which will then provide a folder-like container for all of our backup files.
New Container; click Create; and this will now be the destination for our backups. Now we go to Sequel Server Management Studio. Right-click the database you wish to backup. Tasks; Back Up; and what is now new is that our back up two will be not backup to disk but back up to URL. Click Add; and click New container. You will sign in to your Azure subscription. Select your subscription. Select your Storage Account which is created. And select the container, which is created.
You will need to create a credential to be able to access this container; and credentials do expire. So pick an expiration date that is appropriate for your backup schedule, and click Create Credential. This is a shared access signature which is essentially a log-in for Sequel Server to be able to access your shared storage account. Click OK, and this will be the destination for our backup. Click OK, and the backup runs from the Sequel Server over HGPS directly to your Azure Storage Account on Azure. Backup completed successfully.
At this stage you can now restore from that same blog into your DevDesk or other environments.
- Working with the Query Store
- Temporal tables
- SQL Server on Linux
- Row-level security
- JSON support
- Operational analytics