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: Dear SQL DBA, I’ve noticed that many indexes in my data warehouse aren’t used frequently.
I can’t wait to teach my full day course, SQL Server Index Formulas: Problems and Solutions in Seattle at the PASS Summit on Tuesday, October 25th. Woot! Less than 3 weeks away!
As you tweak and test queries, it’s awfully useful to see how the performance has changed.
What tools in SQL Server will notify you about blocking and help track the queries behind your toughest blocking and deadlocking problems?
Every query tuner wants to explain exactly how much faster we made a query.
But sometimes SQL Server Management Studio adds noticeable overhead to the query duration. For relatively fast queries that return more than a few rows, just the overhead of displaying the results can skew your duration metric.
Should you always index your foreign keys? What if you index them, and then the index never gets used?
Copyright (c) 2024, 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.
