Query Hash Statistics, a query cost analysis tool, now available for download

Some time ago I described the query fingerprint and query plan fingerprint (a.k.a. query hash / query plan hash) features that were added in SQL Server 2008.  A fingerprint identifies all queries or all plans that have the same “shape”.  With query fingerprints you can get the cumulative cost of all executions of a query…

1

T-SQL UDTs. (Huh!) What are they good for?

(The title of this post might seem a little inflammatory, but it’s not just a troll — I really do think that people should seriously question whether it’s wise to use T-SQL User Defined Data Types.  Mostly, though, I just like that Edwin Starr song.)    Let me start this post off by saying that…

7

SQL Server Sizing Resources

Recently, I was asked whether Microsoft had any SQL Server hardware sizing tools.  The asker referred me to http://www.sizinglounge.com as an example of what he was looking for.  (Sizing Lounge apparently allows you to select an app like SAP or Exchange, answer a couple of questions about things like concurrent user counts and desired CPU utilization…

1

Purging Data

This post is about deleting a lot of rows, as you might do in a data archiving or purging task.  By “a lot of rows”, I mean anything from a few thousand rows up to billions.  This may seem elementary, but there are some surprising problems that can appear if you use a simple DELETE…

4

Finding procedure cache bloat

Explicitly parameterizing queries is a well-known best-practice for database app developers.  There are cases where it can make sense to execute a query unparameterized, but, in general, you should default to explicit parameterization.  It can make your queries faster by avoiding unnecessary compilation when the “same” query is run repeatedly with different parameters, and it can reduce…

1