<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Azure Sql on Chris McKelt - Remembering Thoughts</title><link>https://blog.smarttechventures.au/tags/azure-sql/</link><description>Recent content in Azure Sql on Chris McKelt - Remembering Thoughts</description><generator>Hugo -- 0.147.2</generator><language>en</language><lastBuildDate>Wed, 28 Aug 2019 00:00:00 +0800</lastBuildDate><atom:link href="https://blog.smarttechventures.au/tags/azure-sql/index.xml" rel="self" type="application/rss+xml"/><item><title>Using Azure Pipelines to restore a production database to another environment</title><link>https://blog.smarttechventures.au/articles/posts/using-azure-pipelines-to-restore-a-production-database-to-another-environment/</link><pubDate>Wed, 28 Aug 2019 00:00:00 +0800</pubDate><guid>https://blog.smarttechventures.au/articles/posts/using-azure-pipelines-to-restore-a-production-database-to-another-environment/</guid><description>&lt;p>Often we need a fresh copy of the production database in another environment (eg DEV/TEST/UAT). &lt;/p>
&lt;p>Previously this was a tedious task involving getting a backup file, copying it to another location, restoring the database.   Here is a solution to automate this process using Azure Pipelines.&lt;/p>
&lt;h3 id="user-story">User Story&lt;/h3>
&lt;pre>&lt;code>Given a production database exists in subscription 1
When we do a release of the Azure Pipeline named ‘_Refresh Database – DEV’_
Then an copy of production is available in the DEV environment in subscription 2
And permissions are correct for the DEV environment
&lt;/code>&lt;/pre>
&lt;h2 id="pipeline-overview">Pipeline Overview&lt;/h2>
&lt;p>For each environment that you wish to restore into create an Azure Pipeline with 3 stages.&lt;/p></description></item></channel></rss>