1. A Practical Approach to Version Control for SQL Server Steve Jones SQLServerCentral Redgate Software

2. Goals Store database code in version control Track code changes across time Branch and merge changes to database code

3. Get in touch www.voiceofthedba.com sjones@sqlservercentral.com @way0utwest Steve Jones

4. Free Tool Database Lifecycle Management

5. What is version control? …any kind of practice that tracks and provides control over changes to source code. Software developers sometimes use revision control software to maintain documentation and configuration files as well as source code. (Wikipedia) Source Control = Version Control = Revision Control

6. Use version control because neither you nor your developers are perfect.

7. Getting Started Create a location in a VCS respository Script out objects to.sql files Commit files

8. Workflow Check out or open a file Make changes (and test) Save and Commit

9. Demo – Setup in Git

10. Benefits Communication and collaboration History Undo Get back to previous versions Branching/merging Single version of the truth Building block for ALM

11. Demo – Changes, Migrations, and History

12. Teamwork Work should be logically separated Sandboxes should to be used Developers’ work should not conflict But sometimes we work on shared databases, and …

13. Everyone Wants Locking

14. Demo – Locking Objects and Conflicts

15. Branching

16. Example of branching and merging #SQLintheCityUK #SQLintheCityUS

17. Branches can be dangerous

18. #SQLintheCityUK #SQLintheCityUS Demo – Branching and merging

19. Finally Use a VCS, keep control of your code Ensure everyone has the tools Ensure everyone understands the process Write comments for the future you

20. Goals Store database code in version control Track code changes across time Branch and merge changes to database code

21. Want to try the tools you’ve just seen? Visit the Redgate Booth Questions? sjones@sqlservercentral.com @way0utwest #SQLintheCityUK #SQLintheCityUS Fill in your evaluations