Building your database code is an essential practice to ensure that it compiles from source and that dependencies are met. But things can get tricky when you have objects in some databases which is dependent upon objects in other databases – or even circular dependencies.

You’re a DBA, and your development team is all-in on doing DevOps, and they want to include the database. Should your DBA team limit the permissions or options for automation? Or should you instead re-think how your two teams work together?

This post is a part of #tsql2sday, a monthly community ritual where a topic is proposed by a community member and everyone is invited to join in. This month’s topic is from Mohammad Darab, who encouraged us to: “Write your 20 year old self a letter. If you could go back in time and give yourself advice, what would it be?” The advice I would give to my 20 year old self is the same advice I give to myself today, more than 20 years later:

I recent chatted with some folks who have a permissions problem in SQL Server. The permissions problem isn’t technical – it’s a process problem.

Joins are essential. The SQL Corgs introduce you to INNER joins in this animated short.

Why do we “normalize” relational databases, and what are the basics? Awkward Unicorn explains, with a little help from their friends.

Freyja the corgi shares her tips for learning SQL: SELECT, FROM, and WHERE.

Now that I’m getting the hang of this, I think I’m going to do a whole series of shorts on SQL syntax essentials, plus tips and tricks!

I learned to make short form videos with my drawings this week, and, well… things are about to get weirder.