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,511 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
583 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)
484 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,185 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)
250 reads
This script drop all indexes from table, including Primary Key contraint. First it del nonclustered indexes, then clustered and at last - drops PK contraint. This scirpt is useful, when you need drop all indexes, like when doing ETL process.
2004-03-17
541 reads
2006-07-12 (first published: 2004-02-26)
385 reads
Ramesh writes about various indexing strategies that you might use to improve performance.
2004-01-07
10,688 reads
Interesting info about why the optimizer might choose to use a nonclustered index over a clustered index. Links to two other articles that cover each type of index in more detail.
2003-11-04
1,286 reads
By Vinay Thakur
Continuing from Day 5 where we covered notebooks, HuggingFace and fine tuning AI now...
By Steve Jones
This is kind of a funny page to look at. The next page has...
A while ago I blogged about a use case where a pipeline fails during...
I have a table I didn't design that has tons of repeating groups in...
Comments posted to this topic are about the item Writing as an Art and...
Comments posted to this topic are about the item String Similarity II
What is the range for the result from the EDIT_DISTANCE_SIMILARITY() function in SQL Server 2025?
See possible answers