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,250 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,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,188 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)
251 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,690 reads
By HeyMo0sh
Working in DevOps, I’ve seen FinOps do amazing things for cloud cost control, but...
Every organization I talk to has the same problem dressed up in different clothes....
By DataOnWheels
I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...
Comments posted to this topic are about the item The day-to-day pressures of a...
Hello all, I’m looking for advice on how to derive a daily snapshot table...
We need to replace our Windows server running SQL 2017. Any reason not to...
I have some data in a table that looks like this:
BeerID BeerName brewer beerdescription 1 Becks Interbrew Beck's is a German-style pilsner beer 2 Fat Tire New Belgium Toasty malt, gentle sweetness, flash of fresh hop bitterness. 3 Mac n Jacks Mac & Jack's Brewery This beer erupts with a floral, hoppy taste 4 Alaskan Amber Alaskan Brewing Alaskan Brewing Amber Ale is an "alt" style beer 8 Kirin Kirin Brewing Kirin Ichiban is a Lager-type beerIf I run this, what is returned?
select t1.[key]
from openjson((select t.* FROM Beer AS t for json path)) t1 See possible answers