Grant Fritchey Justin Caldicott - Best practices for database deployments
Download as PPTX, PDF0 likes434 views
This document discusses best practices for database deployments. It recommends treating the database like code by putting it under source control and integrating it with the development process. A well-defined, repeatable deployment process is key, working backwards from production and testing changes at each stage. Automation helps speed the process and remove human errors. The overall goal is a tightly coupled, automated workflow that moves database changes reliably through environments like development, testing and production.
Grant Fritchey Justin Caldicott - Best practices for database deployments
- 1. Best Practices for Database Deployments Grant Fritchey, Justin Caldicott #sqlinthecity
- 2. Goals • Understand how to create your own deployment mechanisms • Learn about the tools available for automation of the deployment process • Acquire the knowledge of how to test your deployments #sqlinthecity
- 3. The Database “Problem” • Information persistence layer • Businesses like their data • Keeping that data in place can be work – Which is the start of the “problem” • Object Relational Impedance Mismatch – Which is the rest of the “problem” 3
- 4. The Database “Solution” • Treat it as much like code as possible • Do the following – Work directly with the development team – Define a repeatable process – Put the database into source control – Put tests in place to validate the database – Automate as much of the process as possible • Follow the local development paradigm as much as possible 4
- 5. Process: Team Glue • You must define a process – It’s your process, you define it • Management buy-in • Write the process down – And publish it • Review process regularly • Follow the process – Exceptions have to be exceptional • The process applies to everyone – No, DBAs, you’re not that special 5
- 7. Building a Deployment Process Development QA/Testing Production
- 8. Building a Deployment Process • Production deployment script • Test script on copy of production • Generate script for production from label • Label code in source control • Add changes to source control • Make changes to code • Get code from source control
- 9. Source Control • Two known states – Production – Source Control • Ensures coupling between application and database • History of changes • Auditing
- 10. Demo
- 11. Testing Deployments • ABD – Always Be Deploying • Unit Testing • Continuous Integration • Copies of production
- 12. Demo
- 13. Deploying to Multiple Environments • Multiple moves between multiple environments • Every deployment is practice
- 14. Deploying to Multiple Environments • Multiple moves between multiple environments • Every deployment is practice
- 15. Deploying to Multiple Environments • Multiple moves between multiple environments • Every deployment is practice
- 16. Deploying to Multiple Environments • Multiple moves between multiple environments • Every deployment is practice
- 17. Demo
- 18. Integrating Database with Application • Coupled through source control • Labeled together • Deployed together • Database is deployed first
- 19. Demo
- 20. Deployment Automation • Remove humans from the equation • Speed the process • Make the process repeatable • Take advantage of the tools you know
- 21. Demo
- 22. Summary • Define a process • Work backwards from production • All database code in source control • Integrate tightly with development team • Test and validate all code • Automate as much as possible
- 23. Goals • Understand how to create your own deployment mechanisms • Learn about the tools available for automation of the deployment process • Acquire the knowledge of how to test your deployments #sqlinthecity