You’ve managed to get your team to use version control, you’re using a tool to provision dedicated databases. But it is still a very manual and ‘scripty’ process to get all databases in place for each task for you and your teammates. Of course, you already use PowerShell locally to automate this, but there’s no real standard solution. It works on your pc, and often on someone else’s but in the cases, it doesn’t work, not everyone on the team has the skill or the ambition to fix it.

In this session I will present another approach to get your database provisioned, not by running script by yourself or someone in the team but ‘the system’ will provision your databases just by following the team’s agreed workflow. I'll start by showing you a team that knows that starting new work in Azure DevOps will provision a fresh set of databases. And that’s all they need to know!

Next on the agenda is a solution for easily switching priorities to ‘stash’ your current work (databases), and pick them up exactly where you left off, once the urgent priority is complete. Furthermore, I will walk you through all kinds of speciality pipelines, including the necessary housekeeping of all those provisioned databases.
There will be slides, but it will mainly be code examples that are demonstrated and shared with the attendees.

Get a better developer experience for your team and make database delivery to them self-served and more efficient by getting most out of automation with PowerShell and YAML.