We’ve all seen reindex procedures that rebuild all indexes in a database or all indexes in a database which have less than a specified ScanDensity. This one goes a few steps further. First, the DBA can specify a ScanDensity_Threshold (a min value for ScanDensity), plus a Limit (qty or %). If you specify a ScanDensity_Threshold […]
2005-04-20 (first published: 2005-03-31)
1,866 reads
When it comes to auditing index use in SQL Server databases, I sometimes get overwhelmed. For example, how to do you go about auditing indexes in a database with over 1,500 tables? While auditing a single index is relatively straight-forward, auditing thousands of them in multiple databases is not an easy task. Whether the task is easy or not, it is an important task if you want to optimize the performance of your SQL Server databases.
2005-01-18
3,860 reads
There is nothing spectacular about using indexes per say. However, on many occasions I have come across a variety of SQL coders that never consider validating that the index they think they are using is efficient or even being used at all. We can all put indexes on the columns that we think will be required to satisfy individual queries, but how do we know if they will ever be used. You see, if the underlying table data is constructed, contains, or is ordered in a particular way, our indexes may never be used. One of the factors around the use of an index is its clustering factor and this is what this article is about.
2004-12-23
3,412 reads
SQL Server depends heavily on good indexing to perform well. The optimizer requires relevant and intelligent indexing in order to do its job well. Author Andre Vigneau brings us a script that he uses to detect possible index problems in the database design as well as a number of hints to ensure that your database is performing optimally.
2004-12-08
16,270 reads
Indexing performance has always been the Achilles' heel of SQL Server's full-text feature. Although the search performance itself is fast (very few customers complain about the search speed), users do complain (often loudly and frequently) about how slow the indexing process is–especially for large tables. Here's a few tips for you.
2004-10-15
2,630 reads
Drops all the foreign keys in a database. This is useful when rebuilding data warehouses.
2004-11-30 (first published: 2004-10-13)
1,522 reads
To help maintain index quality, defragging of any given index is a good thing. This will defrag ALL indecies in the current DB. NOTE: Schedule for off-hours operations. For a massive re-write of indecies, change the remarking on "--IF @indid" lines to use reindex instead of just defragging.
2004-09-21
588 reads
Reports on all indexes on user tables within a databaseReports Tables with Missing Clustered indexReports Tables with Missing Primary KeysReports Possible Redundant Index keysReports Possible Reverse Index key
2006-12-21 (first published: 2004-09-16)
492 reads
What happens to SQL Server 2000 indexes over time? Fragmentation is one of the effects and Steve Jones looks at how you can work with and identity fragmentation.
2004-09-15
16,208 reads
This script is supported only in SQL SERVER 2000, This shows only indexes created by users in tables.Parameter @tabela--> You can put the table name and get the information about users indexes in this table.OrYou can put nothing (NULL) and see all tables on the schema and how many indexes each table have.
2004-09-10 (first published: 2004-06-08)
255 reads
By Steve Jones
I have been experimenting with MCP servers in a few ways, including the Redgate...
By Zikato
I deployed a schema change to 30 servers using multi-server query and deploy-at-low-priority. Small...
Fabric deployment pipelines look like they solve CI/CD for Fabric content, especially for people...
Comments posted to this topic are about the item A Challenge of Our Knowledge
Comments posted to this topic are about the item The memory toll of VARCHAR(MAX)...
Comments posted to this topic are about the item Transaction Log Truncation
In SQL Server 2025, where can I find information about items that prevent or delay the transaction log truncation?
See possible answers