Administering SQL Servers for Development Teams. Mike Acord & Tony Sebion Omni Resources

Transcription

1 Administering SQL Servers for Development Teams Mike Acord & Tony Sebion Omni Resources

2 Omni Resources Solutions Group Mike Acord Senior Architect Solutions Group, Omni Resources Tony Sebion Director Solutions Group, Omni Resources MADPASS President

3 Session Agenda Why Is This A Session? A DBA s Responsibilities To Dev Teams Demystifying Developer Work Patterns How Does a DBA Integrate Into A Dev Team?

4 Why Is This A Session? What use is a development DBA? 'None, other than to obstruct me at every opportunity!' 'Well, he'd be more use if he stopped breaking things!' - Doug Burns, Simple Talk Blog,

5 Why Is This A Session? One of the major tension points in any IT department is often between the DBA team and the development team. - Paul Randall, TechNet,

6 Why Is This A Session? DBA s Corner During Any Roadmap Meeting

7 Wow, that s pretty dysfunctional! What s the problem? Not on the same page for priorities and concerns around: Support Responsibilities Design Considerations Deadlines Standards Performance Deployment processes

8 DBA Responsibilities for Production Systems Production SQL n Server Application Server Data-Centric Processing Users Reporting DBA

9 What s Different for Non-Production Systems? Development or Test SQL Server DBA Application Server Being Developed and Tested Data-Centric Processing Being Developed and Tested Reports Being Developed and Tested Developers & Testers

10 Create Non-Prod Support Standards Standards Like Any Other Environment Acceptable uptime & RTO (recovery time objective) Is RPO important? Only the relational DB service? Performance expectations? Will this environment store or process privileged data? Requires interfaces with other environments? Schedule for routine maintenance tasks?

11 So How Do I Try Out New Things? Experiment on an environment that has been established without dev or test uptime expectations. Follow the established software development process for implementation.

12 Software Development Process Most common ones you ll hear about are Waterfall and Agile.

13 Waterfall Development Traditional approach to software development Very linear through the phases of development Late changes are costly Lots of documentation: requirements and design documents Easy to create project schedule and see how long things should take

14 Agile - Deliver Early, Deliver Often Iterative software development Scrum process most popular Prioritized backlog Short sprints with rapid releases Flexible response to change

15 Demo: Scrum Tools

16 Continuous Integration/Continuous Deployment All developer code built and merged together several times per day Frequent committing of code Automated deployments to a separate environment Automated unit tests Constant availability of current build for testing Immediate feedback of breaking changes Deployment becomes routine

17 DevOps Blend of Development and Operations through automation Automation of creation of environment setup and deployments to reduce friction and increase speed Made easier by cloud environments Configuration management of entire environment

18 DBAs Supporting DevOps Provide direct monitoring visibility to production, staging, and test servers in a selfsufficient manner. DEMO using: Adam Machanic s sp_whoisactive Kendra Little s capture loop

19 DBAs Supporting DevOps Provide constant access to this data. Help your developers understand what they re looking at and what they should do about it. Dev team establishes standards and then abides by them.

20 Accommodating Dev Requests Quickly Agile doesn t easily account for delays in fulfilling simple requests. Build self-service tools to accommodate frequent requests. DEMO using: RestoreGene to automate database restores

21 Accommodating Testing DB Resets QA testers will want to run tests, and then reset the database to be able to re-run those tests. DEMO using: Database Snapshot feature in SQL Server Developer & Enterprise Edition

22 Automate Deployment of DB Changes DEMO: Automate Schema Updates On Your SQL Server Database with SSDT

23 Recap Establish standards Understand the user better for example, Agile Thing that support the process Automation or on request deploys and restores Fast turnaround on requests Source control Standards vs. handcuffs Things you can do to support that team Security, performance, enterprise-features

24 Questions? THANK YOU