Introduction Fill Factor is a parameter most of us have ignored because there is no definitive way to calculate what the correct value should be. Part 1 of this series describes a new technique to dynamically determine index fill factors for all indexes within a database. Part 2 covers an analysis of the data collection […]
With origins from the world of “Submarine ‘Dolphin’ Qualification” questions, an “Oolie” is a difficult question to answer, or the knowledge or fact needed to answer such a question, that may or may not pertain to one's duties but tests one's knowledge of a system or process to the limit. Introduction Contrary to what many […]
In which SQL Server stubbornly insists on doing key lookups way, way past the tipping point.
When databases are being designed and developed, your developers might have overlooked creating clustered indexes on some of your database tables. Having a useful clustered index on your tables will improve the performance of your queries. Here Greg Larsen shows a simple script to identify those tables in your database that don’t have a clustered index.
We’ve blogged a couple times about how clustered index key columns get stored in your nonclustered indexes.
But where they get stored is a matter of weird SQL trivia. You see, it depends on how you define your nonclustered index.
Aaron Bertrand kicks off his "Performance Myths" series, showing a "redundant" non-clustered index outperforming the clustered index with the same key.
Get the list of the tables on the server which dont have the clustered index.
SQL Server Clustered indexes can have enormous implications for performance of operations on a table. But are there times when a SQL Server non-clustered index would perform better than a clustered index for the same operation? Are there any trade-offs to consider? Check out this tip to learn more.
I run this code on SQL Server 2019:
DBCC CLONEDATABASE(imdb, imdb_dev)I then change to the cloned database, imdb_dev, and run some queries. I then run this code while testing:
INSERT dbo.Title (TitleID, Title, DateReleased) VALUES (3234, 'Maestro', '2023') GOWhat happens? See possible answers