5/23/2023 0 Comments Teamcity restore from backupUse the “+ Add” button at the bottom of the page to create a new container. Inside the storage account, click the Containers link at the top of the page. If you do not already have a storage account, create a new one. If you prefer to use an online tool, simply log into the Azure Management Console and click the link on the left for Storage. There are two ways you can add a container to your storage account on Azure. We used the certificate method described in this guide to set up our PowerShell tools (there’s no need for us to reiterate the steps here). Second, we need to install the Azure PowerShell tools and map them to our subscription. If you’re version number is lower than, you will need to update SQL Server to use this guide. Check your SQL Server version to make sure you have the tools you need (run SELECT SQL Management Studio to see your version number). The cmdlets that allow you to backup and restore databases are found in the SQL Server PowerShell (SQLPS) utility of SQL Server 2012 SP1 CU4 or higher. Host the backup and restore scripts on the CI serverĬreate build steps in TeamCity to run each scriptįirst things first, the PowerShell cmdlets we need are in two places. Set up remote PowerShell access on each serverĪdd remote certificates to trusted store on appropriate machinesĬreate a SQL credential on all SQL Server instancesĬreate scripts to perform the backup and restore operations for each server Set up the Azure PowerShell tools in all environments (local and remote)Īdd a storage container to our storage account on Azure Make sure SQL Server version is 2012 SP1 CU4 or higher (build ) Our goal is to consolidate this information in one place for others who wish to accomplish the same task. However, the information we needed to accomplish our task was spread out around the web. Our CI, QA and UAT environments are hosted on Windows Azure, so we immediately turned to the Azure PowerShell tools for our solution. We quickly saw an opportunity for automation, and sought out the means to script database promotion from one environment to another. But we were manually moving new database files into our Quality Assurance (QA) and User Acceptance Testing (UAT) environments when there was a database schema change. There was already a good automation process in place for pushing our code out to different environments using TeamCity, our Continuous Integration (CI) server. Read more.Ī current medical software project here at Orthogonal involves a lot of Microsoft SQL database development. Pathfinder Software changed its name to Orthogonal in 2016. This post was previously on the Pathfinder Software site.
0 Comments
Leave a Reply. |