There are a number of tools Octopus Deploy integrates with to deploy to SQL Server, and it can be a bit overwhelming to get started. This section will help get started on automating deployments to SQL Server.
We have written a number of “iteration zero” blog posts that examine the benefits and approaches to automating database deployments:
- Why consider database deployment automation?
- Database deployment automation approaches
- How to design an automated database deployment process
- Automated database deployment process: case study
- Implementing an automated database deployment process
- Pitfalls with rollbacks and automated database deployments
Common deployment process patterns
There is a learning curve with adopting automated database deployments, and that can lead to quite a bit of trepidation, after all, databases are the lifeblood of most applications. There are some common deployment patterns you can adopt to build trust and level-up tooling knowledge quickly.
Learn more about common patterns.
The database account used in the database deployment process needs enough permissions to make appropriate changes, but it should not have so much control it could damage an entire server.
Learn more about user permissions for SQL Server.
We have written a number of guides and blog posts on the various tooling Octopus Deploy interacts with.
- Docs: Deploying to SQL Server with Redgate SQL Change Automation
- Docs: Deploying to SQL Server with a DacPac
- Blog: Using DbUp and Workers to Automate Database Deployments
- Blog: Deploying to SQL Server with Entity Framework Core
- Blog: Ad hoc SQL data scripts
See working examples on our samples instance.
- Blog: Automated blue/green database deployments
- Blog: Using ad-hoc scripts in your database deployment automation pipeline
Help us continuously improve
Please let us know if you have any feedback about this page.
Last updated Sunday, January 1, 2023