SQLNorthEast (NEWCASTLE) SQL SERVER USER GROUP

Network, learn, ask a question, meet other folk, get fed - these are all things that happen at user group events. These events are a really great opportunity to socialise in an informal learning experience - if you want your own exposure then come and do a 1 - 5 minute nugget in front of your peers or use it as an opportunity to ask for help with any issues that may arise at work.

Remember to tell your friends and colleagues; make sure you register as soon as you can.

5.45pm – 6:15pm Registration and networking
6:20pm - 7:20pm – Database version control and deployment: model or migration scripts? - Alex Yates
7:20 - 7:40pm - Break
7:40pm – 8:20pm - Database DevOps Anti-patterns - Alex Yates
8:20pm - Feedback and Close

Finally: Drinks on the Quayside :)

Featured Presentations:

Database version control and deployment: model or migration scripts?

Alex Yates

For the last few years Microsoft and others have been promoting declarative, model-based database development. For many this is the way forward – design the desired state and let software work out the upgrades. Gone are the days of managing endless upgrade scripts and manual deployments.

At the same time, leaders and shakers of our industry including Jez Humble, Pramod Sadalge and Paul Stovell promote an iterative, migration script driven approach asserting that deployment scripts should be tested early and not generated by software. They often assert that a disciplines migrations approach is the only reliable way to achieve database continuous delivery.

So many presenters have opinions that one of the approaches is the “right” way and the other is the “wrong” way. However, like with most complicated problems, the truth is that it depends.

I’ll illustrate the relative strengths and limitations of each approach with a simple scenario. I’ll describe teams and databases that are better suited to a model or a migrations approach, and whether it’s possible to get the best of both worlds.

You’ll leave this session with a better understanding of what options are available to you and which is more likely to work for your team. With so many teams struggling to apply continuous delivery to their databases it’s important to consider whether the problems you are facing are because you have taken an approach which is fundamentally unsuitable for your database.

Database DevOps Anti-patterns

Alex Yates

DevOps has revolutionised our ability to deliver customer value.

Updates aren’t held up in 6-month release cycles. We’ve automated tests and deployments collaboratively so we know updates work. A virtuous cycle of innovation and testing allows us to build better, more reliable products faster and cheaper.

However, while that’s great in theory, I’ve seen people screw up spectacularly when applying DevOps to relational databases.

In this light-hearted session I’ll present the 15 most popular ways to screw up, resulting in painful, fragile deployments and expensive legacy databases that no-one likes to maintain.

A session for developers *and* DBAs.

About Alex:

Alex loves DevOps. He also loves databases.

Alex has been helping data professionals apply DevOps principles to relational database development and deployment since 2010. He's most proud of helping Skyscanner develop the ability to deploy 95 times a day. Originally for Redgate, later for DLM Consultants, Alex has worked with clients on every continent except Antarctica - so he's keen to meet anyone who researches penguins.

A keen community member, he helps organise the London Continuous Delivery meetup and SQL Relay. He blogs at workingwithdevs.com, speaks wherever they'll let him and manages the DLM Digest monthly email: a report on the latest database DevOps news/tutorials.

He's quite fond of Nutella. And otters. (Not together).