How SQL Change Automation helps you deliver value faster
•Als PPTX, PDF herunterladen•
0 gefällt mir•167 views
Learn how Redgate tools enable you to speed up software delivery with reliable, repeatable processes that remove the database bottleneck. Learn how you can empower your developers to innovate without sacrificing compliance, and bring DBAs into the SDLC early at critical review points.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie How SQL Change Automation helps you deliver value faster
Ähnlich wie How SQL Change Automation helps you deliver value faster (20)
Mehr von Red Gate Software
Mehr von Red Gate Software (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
How SQL Change Automation helps you deliver value faster
- 1. How SQL Change Automation Helps You Deliver Value Faster
- 2. Kendra Little DevOps Advocate Redgate /KendraLittle @Kendra_Little Microsoft Data Platform MVP and MCM DBA, Consultant, Trainer, Advocate
- 3. Agenda 1. The workforce is evolving 2. Customers are driving products 3. How SQL Change Automation Helps You Deliver Value Faster
- 4. The workforce is evolving Teams are increasingly distributed Skill shortages are increasing
- 5. Distributed teams increase the risks of silos for database changes 0% 10% 20% Failed Deployments & Downtime Slow dev & release cycles Inability to respond to changing requirements State of Database DevOps Report 2019
- 6. A: Lack of appropriate skills in team Q: What is your main obstacle to implementing DevOps? State of Database DevOps Report 2019
- 7. Standardizes practices that ensure stability of code and unify team Reduce manual work to free up time for value- added tasks and learning Compliant Database DevOps fits the evolving workforce
- 8. All responders DevOps Adopters DBAs and Devs with “great” collaboration 41%22% State of Database DevOps Report 2019
- 10. Application code code benefits from standardized practices • Version control • Dedicated development environments • Automated builds
- 11. Database code is comparatively impoverished • No version control in 45% of environments • No automated build & deployment in 66% of environments State of Database DevOps Report 2019
- 12. Standardization need not be rigid Standardization • Version control Flexibility • Branching strategy
- 13. Standardization need not be rigid Standardization • Version control • Continuous Integration Flexibility • Branching strategy • Customize pipelines
- 14. Standardization need not be rigid Standardization • Version control • Continuous Integration • Automate deployments Flexibility • Branching strategy • Customize pipelines • Gates / approvals / timing
- 15. Standardization unifies DBA & Dev functions Audit trail of changes Peer review & collaboration Dedicated environments for experimentation Static code analysis Build & code validation
- 16. Customers are driving products Expect delivery of value more quickly Require you to keep their data safe
- 17. 2018 2019 Teams who deploy database changes more than once a week 40%35%
- 18. Software core to the business “tilts” the playing field in favor of those who use it most effectively “Information Technology and Industry Concentration” · James Bessen · Boston University School of Law, 2017
- 19. Patterns for tempo & stability • Deploy frequently • Backwards compatible
- 20. Patterns for tempo & stability • Deploy frequently • Deploy <> Release • Backwards compatible • Feature flags
- 21. Patterns for tempo & stability • Deploy frequently • Deploy <> Release • Production visibility to devs • Backwards compatible • Feature flags • Listen & change course
- 22. Automation isn’t just about tempo, it also improves code quality Demo: Automation
- 23. How this example worked Azure DevOps • Azure DevOps branch policy & build policy + build pipeline • Azure DevOps Release pipeline with pull request trigger Redgate • Build extension for SQL Change Automation • SQL Clone extension • Release extension for SQL Change Automation
- 24. Support self-service dev environments (with safe data) Automate build & deploy of db code before code review Guardrails for automation
- 25. “We value: Automation as a team player versus automation as a replacement for humans” https://jobs.netflix.com/jobs/869465
- 26. How SQL Change Automation Helps You Deliver Value Faster “If it hurts, do it more often” Stability is critical for success, and DevOps improves this
- 27. Small tasks compose easily Feedback Practice https://www.martinfowler.com/bliki/FrequencyRed ucesDifficulty.html Frequency reduces difficulty
- 28. Most critical for database changes DevOps drives improvements in stability AND tempo https://cloud.google.com/devops/ Stability
- 29. Redgate.com/contact Request a demo Redgate.com/solutions Redgate solutions Redgate.com/webinars Join us for free webinars Get started
Hinweis der Redaktion
- Duration: 75 minutes Level: 200 Stream: Data Management Audience: DBA, Database Developer, Architect, Developer Technology Focus: DevOps Track: Perform As an Architect or Senior Developer, you need to deliver value to your customers more quickly than ever. Your software delivery pipeline can’t be held up by database changes. Instead, you need to bring database changes into your Agile development practices and optimize these practices to find bugs well before they head to production. This means you must find ways of working that bridge longstanding silos between development and operations - even while teams are increasingly distributed across time zones and company cultures. In this session, Microsoft Certified Master Kendra Little will show you how Redgate tools enable you to speed up software delivery with reliable, repeatable processes that remove the database bottleneck. Learn how you can empower your developers to innovate without sacrificing compliance, and bring DBAs into the SDLC early at critical review points. Prerequisites: Basic understanding of TSQL, familiarity with basic source control concepts.
- https://unsplash.com/photos/QLEu_4Xj-fk
- Sample narrative: Having a distributed team isn’t bad, but it makes an existing problem more complex. For database changes, having a culture of working in silos presents big risks. The top 3 are shown here. Breaking down these silos and changing culture with an increasingly distributed team is challenging: We have fewer hallway conversations It’s easy to forget other teams entirely if we never physically cross paths. But breaking down these silos is critical because: “High-performing teams are twice as likely to be developing and delivering software in a single, cross-functional team” 2018 State of DevOps Report · DORA --------------- (question 9 page 11)
- Concern about lack of skills can keep you from taking a leap, because it looks dangerous ------- 70% of hiring managers report a moderate to extreme skills shortage. Reference: 2019 US Salary Guide · Hays · https://www.hays.com/resources/2019-salary-guide/HAYS_2323663 -------- This was 22% Lack of budget was 11% Lack of exec support was 9% Image:https://unsplash.com/photos/mk7D-4UCfmg
- https://unsplash.com/photos/VeUSCLJrLf4
- ”DevOps Adopters” is those who have adopted it across all projects (not just some) Q4 p 7
- https://unsplash.com/photos/IuLgi9PWETU
- A frequent pattern is that agile methods and devops are adopted, but without standardization between how applications are developed and how databases are developed What happens is that we speed up development for how applications work, and standardize practices with great tooling for application code https://unsplash.com/photos/GpNOhig3LSU
- But leave the development of the heart of the application, the database, in an impoverished state Changes here are the most critical – why would we use the LEAST tools to help make it safer and better? Fear of making changes to databases has ironically kept databases in a risky place, where basic tools for auditing and validation are not being used https://unsplash.com/photos/flEStjHTY14
- Note: this slide uses animations to show the points in pairs
- Note: this slide uses animations to show the points in pairs
- Note: this slide uses animations to show the points in pairs
- Note: Gloss over these items quickly: this slide is a quick tee-up for what Chris will be showing next, which touches on just about all of these Can end on this slide OR show the next one, which has the title of Chris’ talk on it Images from Unsplash no attribution required: https://unsplash.com/photos/GokBcmdOI6I https://unsplash.com/photos/8z0LZqRgfaI https://unsplash.com/photos/nE37DZ4GozM https://unsplash.com/photos/T-0EW-SEbsE https://unsplash.com/photos/Zqy-x7K5Qcg
- Narrative: Adopting Agile development methods and DevOps is increasingly common, because customer expectations are higher than ever. A 2018 survey of more than six thousand consumers found that 63% of customers “expect companies to provide new products/services more frequently than ever before” Additionally, eighty percent of customers said “the experience a company provides is as important as its products and services.” Rapid generation of value in stabile environments is more critical than ever, and organizations must do this while protecting against the threat of data breaches Reference: State of the Connected Customer 2018 · Salesforce · http://bit.ly/stateofconnectedcustomer https://unsplash.com/photos/rk_Zz3b7G2Y
- This is a combination of “daily” and ”more than once a week” responses
- https://unsplash.com/photos/SFq3STsAKgc
- Discussion points – this slide is very flexible for the amount of time you can spend here. Separate concepts of deployments and releasing --- example is feature flags Future 30 minute webcast topic: Should you decouple database code and app code? (Discuss different meanings of ”de-couple”, different ways you can configure pipelines, etc)
- Discussion points – this slide is very flexible for the amount of time you can spend here. Separate concepts of deployments and releasing --- example is feature flags Future 30 minute webcast topic: Should you decouple database code and app code? (Discuss different meanings of ”de-couple”, different ways you can configure pipelines, etc)
- Discussion points – this slide is very flexible for the amount of time you can spend here. Separate concepts of deployments and releasing --- example is feature flags Future 30 minute webcast topic: Should you decouple database code and app code? (Discuss different meanings of ”de-couple”, different ways you can configure pipelines, etc)
- https://unsplash.com/photos/mvo-xJE1oFg
- Discussion points – this slide is very flexible for the amount of time you can spend here. Separate concepts of deployments and releasing --- example is feature flags Future 30 minute webcast topic: Should you decouple database code and app code? (Discuss different meanings of ”de-couple”, different ways you can configure pipelines, etc)
- https://unsplash.com/photos/SRtustRynXw
- Automation isn’t something that you set up once and which does a task for you – not anymore. Automation is a team player that team members interact with on a daily basis Stops the assembly line automatically when there’s an issue Prompts for judgment / human interaction Gives information for feedback and analysis https://unsplash.com/photos/VbGYLwHnw88
- “Frequency reduces difficulty” - Martin Fowler - https://www.martinfowler.com/bliki/FrequencyReducesDifficulty.html
- https://www.martinfowler.com/bliki/FrequencyReducesDifficulty.html
- https://unsplash.com/photos/z8_-Fmfz06c