It’s the week of the largest SQL Server conference, the SQLPASS Summit. I’m in Seattle with more than 6,000 other SQL Server professionals. I made it to the Keynote this morning, only to find Rob Farley sitting next to me.
I’ve got a cold and I was waiting for the DayQuil to kick in when the Keynote began. If you’ve ever met Rob, you know I was in no danger of falling asleep.
Sometimes clever developers let you try out cloud services with very little work on your part. This is one of those times - get ready for “Playing with Azure Search: No Installation Required.”
As a database administrator or developer, you’ll get into trouble fast if you try to force all your code and processes into a database shaped hole. You have to be creative when you problem solve – and when you communicate! So how do you cultivate creativity?
If you use SQL Server’s blocked process report or collect deadlock graphs, occasionally you’ll come across things that look like this:
waitresource=“PAGE: 6:3:70133 " waitresource=“KEY: 6:72057594041991168 (ce52f92a058c)”
The bigger your indexes are, the harder your index maintenance falls. Is it better to rebuild big indexes? Or should you reorganize?
I get a lot of requests about which books are helpful to learn performance tuning and database design. I totally get that – I still like learning with books. It doesn’t mean training videos or blogs are any less cool. They can all work together.
Should you look at automatically created statistics on your tables in SQL Server to help you design better indexes? Learn why in this 20 minute video, or subscribe to the Dear SQL DBA podcast.
No time to watch? Scroll on down, everything is written in article form below the video.
Here’s this week’s question:
Copyright (c) 2025, Catalyze SQL, LLC; all rights reserved. Opinions expressed on this site are solely those of Kendra Little of Catalyze SQL, LLC. Content policy: Short excerpts of blog posts (3 sentences) may be republished, but longer excerpts and artwork cannot be shared without explicit permission.