- Are you lumbered with a shared “Wild West” dev database? Do you struggle to manage concurrent development tasks?
- Developers: Is it a pain getting the dev and test environments you need, including realistic and up to date test data?
- DBAs: Are all these requests for dev and test databases getting in the way of important production work? Are you concerned about prod data leaking into the dev/test domain?
If these problems resonate, this session offers you a practical solution. One that requires collaboration between developers and DBAs – and which benefits everyone.
DevOps promotes self-service access to usable test data – but so many developers are lumbered with shared development databases which are often out of date and contain sensitive data. It’s difficult to isolate the development of different features, so they are rolled together into big releases. It’s no wonder database deployments are often expensive, complicated and risky.
What if it was possible for developers to provision themselves with a disposable, masked copy of last night’s production 64 TB database on either their regular laptop or a shared test server, with limited storage, in a matter of seconds? What if it was as easy as “git clone f5”?
In this session attendees will learn to use GitHub, Docker, SSDT and PsDatabaseClone to unshackle themselves from “Wild West” dev databases and empower them to use modern branching techniques and Azure DevOps to continuously deliver their updates to production.
Why I Want to Present This Session:
I’ve been helping folks to adopt database DevOps since 2010. In my experience, the biggest problem for the vast majority of folks is reliance on a shared development database.
I want you to delete your shared dev database – and never look back.
Image source: Michael Neel, Wikimedia, shared under Creative Commons Attribution 2.0 Generic