Find Unindexed Foreign Keys (2005)
This script will find foreign keys (on referencing table) that are not indexed in SQL Server 2005.
2011-12-20 (first published: 2007-08-10)
3,758 reads
This script will find foreign keys (on referencing table) that are not indexed in SQL Server 2005.
2011-12-20 (first published: 2007-08-10)
3,758 reads
Calculates server uptime in days, hours, and minutes. Also calculates the UTC date (smalldatetime) when the server was started.
2011-11-17 (first published: 2007-08-31)
2,440 reads
To report indexes proposed by the database engine that have highest probable user impact. Note that no consideration is given to 'reasonableness' of indexes-- bytes, overall size, total number of indexes on a table, etc. Intended to provide targeted starting point for holistic evaluation of indexes.
2007-08-17
983 reads
This is an enhanced version of my previous script: Prioritize Missing Index Recommendations (2005).To aid in evaluation of whether the recommended index is reasonable, I have added :1. counts for key columns and the total columns of the recommended index 2. the length/bytes for both key and all columns Note this is 'per row', not […]
2007-08-17
1,850 reads
By Steve Jones
Fear is fueled by a lack of imagination. The antidote to fear is not...
The slidedeck and the SQL scripts for the session Indexing for Dummies can be...
By Chris Yates
Change is not a disruption in technology; it is the rhythm. New frameworks appear,...
Comments posted to this topic are about the item Building AI Governance and Policies-...
Why is sql doing a full scan VS seeking on the index? I've included...
We have a report that has multiple tables that list the top 15 performers...
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