Reports index stats, index size+rows, member seek + include columns as two comma separated output columns, and index usage stats for one or more tables and/or schemas.
2012-12-27 (first published: 2008-08-01)
7,886 reads
Lists details for all indexes on one or more tables / schemas, including row count and size. The non-pivot version also gives data type and other details for the columns.
2013-10-02 (first published: 2008-08-01)
3,687 reads
Lists details for all indexes on one or more tables / schemas, including row count and size. This version outputs the member seek + include columns as two comma separated output columns.
2009-01-19 (first published: 2008-08-01)
2,468 reads
Are you rebuilding statistics twice on your tables? Longtime expert, Andy Warren, shows why you might be asking more work of your SQL Server than is required.
2008-07-29
9,117 reads
Expert SQL Server trainer Andy Warren brings us a new article on a lesser used feature in SQL server 2005: the ability to disable an index.
2008-07-22
11,024 reads
In this script we create a temporal table and then review all indexes with next conditions.
avg_fragmentation_in_percent > 10 % or avg_page_space_used_in_percent > 90 %
2008-09-05 (first published: 2008-07-10)
4,640 reads
Generate Script to create all secondary indexes for a database. I have included the ability to generate online indexes if possible and the ability to move to another file group.
2011-09-23 (first published: 2008-07-05)
3,226 reads
Manual SP to Index Defrag a SQL 2000 database on SQL 2005 that run at spesific times at night
2013-12-17 (first published: 2008-05-07)
3,638 reads
Indexing a SQL Server database in some respects is considered both an art and a science. Since this is the case, what are some considerations when designing indexes for a new database or an existing one in production? Are these the same types of steps or not? Do any best practices really exist when it comes to indexing? Where does indexing fall in the priority list from an application or production support perspective?
2008-04-03
4,878 reads
When is it okay to let SQL Server to make a statistic for columns in your queries, and when should you take those statistics and make an index out of them? What I do is to test all of my procs, and if they generate system statistics (_WA_SYS%), then I add an index to the table for the column in the statistic. But is this a good practice?
2008-03-11
3,488 reads
In today’s data-driven world, having the right tools to manage and process large datasets...
By Steve Jones
flichtish – adj. nervously aware how much of your self-image is based on untested...
In a previous post we went through how to use Docker Build Cloud to...
I took a backup with the CHECKSUM option, which was successful and showed no...
Comments posted to this topic are about the item Realities of Predictive Analysis
Just came across something weird. Was wondering if anyone else has ever seen this....
I have a table in SQL Server 2022 that is an XML data type. I have an index on this column and want to create statistics using CREATE STATISTICS for some of the data in the column. What should I do?
See possible answers