2024-01-10
523 reads
2024-01-10
523 reads
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 […]
2019-08-27
3,922 reads
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 […]
2019-08-08
6,300 reads
In which SQL Server stubbornly insists on doing key lookups way, way past the tipping point.
2019-01-04
2,905 reads
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.
2018-05-29
4,777 reads
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.
2018-05-25
3,638 reads
Aaron Bertrand kicks off his "Performance Myths" series, showing a "redundant" non-clustered index outperforming the clustered index with the same key.
2017-04-17
5,314 reads
2015-08-06
1,991 reads
Get the list of the tables on the server which dont have the clustered index.
2014-02-24 (first published: 2014-02-17)
1,377 reads
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.
2013-10-10
6,323 reads
By Chris Yates
Change is not a disruption in technology; it is the rhythm. New frameworks appear,...
No Scooby-Doo story is complete without footprints leading to a hidden passage. In SQL...
By James Serra
A bunch of new features for Microsoft Fabric were announced at the Microsoft Fabric Community...
Comments posted to this topic are about the item Don't Forget About Financial Skills
Comments posted to this topic are about the item Building a Simple SQL/AI Environment
Comments posted to this topic are about the item Checking Identities
The DBCC CHECKIDENT command is used when working with identity values. I have a table with 10 rows in it that looks like this:
TravelLogID CityID StartDate EndDate 1 1 2025-01-11 2025-01-16 2 2 2025-01-11 2025-01-16 3 3 2025-01-11 2025-01-16 4 4 2025-01-11 2025-01-16 5 5 2025-01-11 2025-01-16 6 6 2025-01-11 2025-01-16 7 7 2025-01-11 2025-01-16 8 8 2025-01-11 2025-01-16 9 9 2025-01-11 2025-01-16 10 10 2025-01-11 2025-01-16The docs for DBCC CHECKIDENT say this if I run with only the table parameter: "If the current identity value for a table is less than the maximum identity value stored in the identity column, it is reset using the maximum value in the identity column. " I run this code:
DELETE dbo.TravelLog WHERE TravelLogID >= 9 GO DBCC CHECKIDENT(TravelLog, RESEED) GO INSERT dbo.TravelLog ( CityID, StartDate, EndDate ) VALUES (4, '2025-09-14', '2025-09-17') GOWhat is the identity value for the new row inserted by the insert statement above? See possible answers