Unit Testing & Intelligent Query Processing

Actually, these two topics don’t have anything to do with one another. I just ran out of days to promote everyone individually who was taking part in putting on Redgate Streamed.

Steve Jones

Steve is one of the better people I know when it comes to the wisdom and need for testing. Speaking only for myself, I kind of hate setting up tests. Yes, I know how vital they are. Yes, I know they make an enormous positive impact on our ability to generate better code, faster. Yes, I know they’re a fundamental aspect of DevOps. Yet, they’re a pain the bottom.

However, Steve has a way with them. He really does make them look easy. If you’re like me and not a huge fan, then his session “The Basics of Unit Tests With tSQLt” is for you.

If, on the other hand, you don’t think automated testing should be playing a part in your database development and deployments, then by the gods, you MUST attend this session. You need to learn the error of your ways.

Seriously though, Steve’s approach on this stuff is well worth your time. I promise, you’ll learn things you didn’t know.

Kathi Kellenberger

Kathi and I have been friends ever since I went to the very second, #SQLKaraoke event. Yeah, I missed the first one. Anyway, she and I have been friends a long time. She’s a great person. More than that though, she really knows what she’s talking about. This is especially true when it comes to queries.

One of the most exciting, and sadly necessary, new bits of functionality in Azure SQL Database and SQL Server 2019 (to a lesser extent, 2017 too), is the ability of the query optimizer to literally modify plans on the fly. This is called Intelligent Query Processing. It’s a game changer. Best of all, it’s a game changer that doesn’t really require you to do anything.

However, you’re going to want to know exactly how it works, what it does, and how you’re most likely to benefit from Intelligent Query Processing. Further, you’re going to want to know what it doesn’t do. Kathi is going to cover all this, and maybe a bit more, in her session called “An Introduction to Intelligent Query Processing”.

Redgate Streamed

These sessions are all part of our new event called Redgate Streamed. Follow the link to see all the other sessions, or read back through my blog where I call out the other presenters by name. This particular event is absolutely a community, #SQLFamily, focused event. We’re putting on material that we think is useful to you, right now. It’s not Redgate material (although, some of it is clearly very adjacent to our material). Please, follow the link, get registered, and get your learn on.

Also, read through the registration page. We’re trying a bunch of different experiments to make this as much of a copy of in-person events as we can. We’re giving you as many opportunities as possible to directly engage with myself and all the other advocates as well as various other Redgaters, just like stopping by our booth.

Also, this week would have been SQLBits. That event is very near and dear to my heart, even though I’ve only attended a few of them. It’s just special. In honer of SQLBits, first, we’re having a pub quiz with the guys at DBAle. So get signed up for that. Second, on Friday, many of the presenters will be in fancy dress, in honor of the Friday party at SQLBits.

Finally, Redgate is donating the money we would have spent at SQLBits to the WHO. However, for every single registration we get to Redgate Streamed, we’re going to add more money on top. So, just you registering acts as a fundraiser for the WHO. Please, help us out.

2 thoughts on “Unit Testing & Intelligent Query Processing

  • Bryant McClellan

    I’m looking forward to Steve Jones’ presentation. We are a tSQLt shop and have been for at least 4 years. In most databases we have way more test objects than anything else. We teach tSQLt internally. We get very few employees or contractors who are fluent in tSQLt so we pretty much have to train.

    We use SSDT for database projects and distribute the tSQLt framework, along with our extensions, via .dacpac references. That makes things fairly straightforward for both new project creation and managing tSQLt updated.

    Like DevOps pipelines there is no free lunch. You will absolutely slow down development when you start unit testing database. There is a huge benefit on the other side when you start shipping more new product and fewer bug fixes because you caught them in unit testing.

Please let me know what you think about this article or any questions:

This site uses Akismet to reduce spam. Learn how your comment data is processed.