Automate Database Deployment - SQL In The City Workshop
Download as pptx, pdf4 likes1,449 views
The document outlines the principles and practices of automating database deployments through continuous delivery, emphasizing the significance of version control and integration into the release pipeline. It highlights the distinct concepts of continuous delivery versus continuous deployment and the common challenges faced in database management. Additionally, it presents strategies for managing changes, testing, and ensuring reliability in deploying database updates.
Automate Database Deployment - SQL In The City Workshop
- 1. Automate Your Database Deployments Continuous delivery for databases Grant Fritchey Red Gate Software
- 4. Development Continuous integration Build Test Publish Sync ALTER TABLE foo… Deployment script Release management Artifact repository Production Trigger Review, Backup & deploy Source control QA / Test / Pre-production Continuous delivery for databases Database release pipeline Continuous Integration Development ProductionTesting Operations Database development and change management
- 5. Development Continuous integration Build Test Publish Sync ALTER TABLE foo… Deployment script Release management Artifact repository Production Trigger Review, Backup & deploy Source control QA / Test / Pre-production Continuous delivery for databases In this presentation Database release pipeline Continuous Integration Development ProductionTesting
- 6. Goals • Understand the patterns and practices for automating database deployments. • Learn about the advantages continuous integration brings to a release pipeline. • Understand the challenges databases present for continuous delivery.
- 7. Continuous delivery – what it is and isn’t Common misconception: Continuous delivery = Continuous deployment But in fact: Continuous delivery means making sure your database changes are always production-ready.
- 8. Recap: Continuous Delivery Development Test Production Release pipeline Approval gate
- 9. Four key stages of the deployment pipeline SOURCE CONTROL CONTINUOUS INTEGRATION AUTOMATED TESTING AUTOMATED DEPLOYMENT
- 10. Get your database under control • Use version control for all code (including tests) • Commit early, commit often • Use tools o If it’s hard, people don’t do it • Train people • Build often SOURCE CONTROL
- 11. Continuous Integration • Requires • Code repository • Build automation • Delivers • Functional testing • Delivery testing • Artifact generation CONTINUOUS INTEGRATION: FUNDAMENTALS
- 12. Database Deployments in CI • Complete deployment • Fast • Partial build validation • Functional validation • No artifact • Incremental deployment • Longer • Harder • Complete build validation • Generates artifact CONTINUOUS INTEGRATION: FUNDAMENTALS
- 13. Demo
- 14. Development Continuous integration Build Test Publish Sync ALTER TABLE foo… Deployment script Release management Artifact repository Production Trigger Review, Backup & deploy Source control QA / Test / Pre-production Continuous delivery for databases Focus here Build out your release strategy Continuous Integration Development ProductionTesting
- 15. Automation
- 18. Development Continuous integration Build Test Publish Sync ALTER TABLE foo… Deployment script Release management Artifact repository Production Trigger Review, Backup & deploy Source control QA / Test / Pre-production Continuous delivery for databases Repository might be separate piece of software or part of release management software Continuous Integration Development ProductionTesting Operations Database development and change management
- 19. Demo
- 20. Pre-production is a dry-run • Staging matches production • As close as possible • Can use diff tool • Or backup and restore AUTOMATED DEPLOYMENT
- 21. Development Continuous integration Build Test Publish Sync ALTER TABLE foo… Deployment script Release management Artifact repository Production Trigger Review, Backup & deploy Source control QA / Test / Pre-production Continuous delivery for databases Continuous Integration Development ProductionTesting Operations Database development and change management
- 22. Wait…
- 23. Check for database drift • Last-minute hotfix • Manual emergency fixes • Unknown changes AUTOMATED DEPLOYMENT
- 24. Ready to go now?…
- 25. Plan for things to go wrong …you need a rollback and recovery strategy AUTOMATED DEPLOYMENT
- 26. Protection • Backups • Snapshots • Rollback scripts • A/B or blue/green deployments • Roll forward scripts AUTOMATED DEPLOYMENT
- 27. Demo
- 28. Recap: Continuous Delivery Development Test Production Release pipeline Approval gate
- 29. Documentation and resources • Continuous Delivery by Jez Humble and David Farley (Addison Wesley) • The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win by Gene Kim, Kevin Behr and George Spafford (IT Revolution Press) • The Goal: A Process of Ongoing Improvement by Eliyahu M. Goldratt and Jeff Cox (Gower Publishing Ltd.) • Agile Organization by the agile admin (theagileadmin.com) Further resources: • Database Delivery Learning program: www.red-gate.com/delivery • Patterns and practices on Simple-Talk • Tutorials in Red Gate training academy • www.youtube.com/user/RedGateVideos - for recorded seminars
- 30. Want to try the tools you’ve just seen? Come to our Hands-on Labs
- 31. Image sources Author Source Information William Warby Flickr Glass Man - Flickr. This file is licensed under the Creative Commons Attribution 2.0 Generic license. Perry McKenna Flickr Headless Horse – Flickr. This file is licensed under the Creative Commons Attribution 2.0 Generic license. William Warby Flickr Gears – Flickr. This file is licensed under the Creative Commons Attribution 2.0 Generic license. Ross Harmes Flickr Gear for lightweight snow camping – Flickr. This file is licensed under the Creative Commons Attribution 2.0 Generic license. Val Gardena – Gröden Marketing Flickr Fis Ski World Cup Val Gardena Gröden – Flickr. This file is licensed under the Creative Commons Attribution 2.0 Generic license Paul Pehrson Flickr Ice cream sundae - Flickr. This file is licensed under the Creative Commons Attribution 2.0 Generic license
Editor's Notes
- #2: Grant will be modifying the talk w/c 1st September to shorten and refocus 50:50 ratio of content on CI and release management Make it clearer that CI is the natural next step on from version control Go into more detail on CI as a process Cut out demo on version control as an entity Reduce rollback and recovery slides to one slide
- #7: We’ll also demo a database change from the point of version control all the way through to release to production, so you can see it in practice.
- #8: Animated slide shows that people often think continuous deployment is the same as continuous delivery – but this isn’t the case. This is an important distinction for database professionals. Continuous delivery and continuous deployment are very different beasts. Continuous delivery is about always being ready, at any point in time, to release your software. Continuous deployment, on the other hand, is about having such confidence in your automated testing and deployment procedures, that you automatically release a change straight from development into production (via other test servers of course!) without human intervention.
- #9: See where continuous delivery fits in on the continuum of a release pipeline – and continuous processes. Important to emphasise the quality check at the approval gate stage for continuous delivery – this is a chance for DBAs to review scripts before they enter the production environment.
- #11: From a technology standpoint, before you think about continuous delivery, you need to get your database under control. This is a quick recap of the version control and CI talk in the series – essentially, version control and continuously integrating and reporting back on builds needs to be in place.
- #12: Show that it exists in source control. Show the folder so that they can see the create scripts, it’s not a series of changes scripts.
- #15: Detailed CI demo. Use TeamCity. Emphasize the generation of the artifact, nuget package.
- #21: Introduce octopus. Using artifact. Primarily test and talk about artifact. Works in TFS too through a pretty gui.
- #22: Staging should be as close as possible an environment to Production – here are some characteristics to think about. Idea is that you can use Staging/pre-Production to debug and diagnose any issues before a release enters the (locked down) Production environment.
- #24: Hold on – you also need to check Production is still in the same state as you expect – what if the database has ‘drifted’ – especially the schema - since you last looked?
- #25: Need to be aware of unexpected changes being made to Production – or risk deployment failing, or data loss.
- #26: Ok, so we’ve determined there’s been no drift. Are we ready to go? Not quite yet…
- #27: Even after all the testing, the review, the checks, we should still obviously plan for things to go wrong. Build out a rollback and recovery strategy – there are several options to consider.
- #28: Very basic first step is to have a backup of your Production environment. You probably have these already running regularly!
- #29: Pre-prod and the generation of a t-sql script. Also mention drift resistance there.
- #30: See where continuous delivery fits in on the continuum of a release pipeline – and continuous processes. Important to emphasise the quality check at the approval gate stage for continuous delivery – this is a chance for DBAs to review scripts before they enter the production environment.