Being a DBA, developers approach me with questions like can you run this query for me in production?
WHERE UnitPrice = 32.6
Lets, say the table contains few billion rows and UnitPrice is not an indexed column, then query would take ages to provide the result. Not just that, it causes a massive I/O on a busy production database.
For the above situation, I would usually ask the developer, “Would you need a accurate value or is it ok if it is approximate?”. If approximate numbers are fairly sufficient then, one can answer these type of questions without actually querying the table. How?
Simple – STATISTICS is the word 🙂
To find the statistic that will be useful for the query, please use the following script and provide the table name and column name. The script provides the statistic name we should be checking.
Declare @table_name varchar(100)
Declare @Column_name varchar(100)
SET @table_name = ‘FactInternetSales’
SET @Column_name = ‘UnitPrice’
SELECT OBJECT_NAME(s.object_id) AS object_name,
COL_NAME(sc.object_id, sc.column_id) AS column_name,
s.name AS statistics_name
FROM sys.stats AS s
JOIN sys.stats_columns AS sc
ON s.stats_id = sc.stats_id
AND s.object_id = sc.object_id
OBJECT_NAME(s.object_id) like @table_name
COL_NAME(sc.object_id, sc.column_id) like @Column_name
ORDER BY s.name;
After finding the statistic name, just go to the table, expand “Statistics” and double click on the stat that you are interested in. The click on the details section, find the value interested in on “Range_HI_Key” Column and observe the “EQ_Rows” section to get the approximate number of rows.
Most of you would know that statistics can be used to find query estimates but few (I guess) would use it operationally for these kind of requests. One can also use them to estimate for queries of this type too
WHERE UnitPrice > 40 — ( Possible but can get little tricky at times, more of it on upcoming posts 🙂 )
Few quick pointers:
The above method relies on the following prerequisites
* Either Auto create Stats should be turned on or the column should be the leading column of any index for the statistic to be present. Auto Create Stats are on by default
* For the stat to be reasonably accurate, one needs to have Auto Update Statistics on ( which is also “on” by default )
* Automatically created statistics are named like ‘_WA%’. For a column to have a auto created stat, the column should have been queried at least once since database creation. Indexed column would not need auto created statistics
* To figure out when was the statistic last updated, use the following query
sp.stats_id, name, filter_definition, last_updated, rows,
rows_sampled, steps, unfiltered_rows, modification_counter
CROSS APPLY sys.dm_db_stats_properties(stat.object_id, stat.stats_id) AS sp
WHERE stat.object_id = object_id(‘people_Data’)
and name like ‘_WA_Sys_0000000D_1273C1CD’;
There is always more to statistics. Will cover them in upcoming posts.