Automated database deployments is a critical aspect of any continuous integration pipeline. The tooling today has made it very easy to get that added, especially if you use Octopus Deploy and Redgate DLM Automation. It is very easy to add the necessary step templates into Octopus Deploy to get Redgate
The previous post [https://www.codeaperture.io/2017/11/27/automated-developer-machine-setup-part-1-introduction-and-dism/] in this series talked about why it is important to automate developer machine setup as well as getting Windows configured using DISM. This article will dive into automating the install of a common developer tool suite. A Common Time-Suck:
The tooling necessary to incorporate DevOps practices is already out there. There are many different flavors of build tools, Jenkins, TeamCity, VSTS, AppVeyor, and Bamboo. Release management is covered by Octopus Deploy, Release Management, and Bamboo. And finally, database automation tooling provided by Redgate SQL Toolbelt and Microsoft SSDT. The
Back in the article How Redgate Helped Define our Process [https://www.codeaperture.io/2016/09/13/how-redgate-helped-define-our-process/], there was this small blurb about SSDT: > Microsoft SSDT Tooling Considered - the increased cost of licenses forced us to take a hard look at Microsoft's SSDT tooling. Could it do what
Microsoft has made their VSTS (Visual Studio Team System) build system very flexible. It doesn't matter if you host it on-premise or in the cloud, you can easily extend out functionality by importing existing custom tasks through the marketplace [https://marketplace.visualstudio.com/vsts] or write your own custom tasks.
One of the less common known facts about Redgate's DLM Automation suite is purchasing license grants the purchaser the right to use to command line versions [https://documentation.red-gate.com/display/SC12/Integrating+the+command+line+with+applications] of SQL Data Compare and SQL Compare. Seems strange, right? Well when