Getting a query plan
Query plans are an essential tool when doing performance tuning. When looking at a query plan you should be aware...
2014-02-19
1,479 reads
Kenneth Fisher
T-SQL Tuesday #51: Doubledown disaster
Jason Brimhall is hosting the 51st T-SQL Tuesday this month with “Place your bets!.
It’s always a gamble when buying a...
2014-02-14 (first published: 2014-02-11)
1,574 reads
Transactions: What commands aren’t allowed?
Transactions are great tools that every DBA and developer should learn how to use. Unfortunately not everything can be put...
2014-02-13 (first published: 2014-02-05)
4,549 reads
Check your SQL Agent history settings before it’s too late!
A little while back I was doing some research into a failed job and ran into a slight problem. The...
2014-02-10
891 reads
Negative session_ids
I probably had the most fun all week when a query I was running came up blocked. Sounds strange right?...
2014-02-03 (first published: 2014-01-27)
2,164 reads
Transactions: Creating a single restore point across multiple databases.
This is a disaster and recovery trick I’ve found to be useful for developers with batch processes that hit multiple...
2014-02-02
1,359 reads
Using sys.dm_exec_sql_text() to figure out blocking is sometimes flawed.
I frequently rely on joining sys.dm_exec_requests and sys.dm_exec_sql_text() to know what queries are running on a system and when I...
2014-01-29
1,139 reads
Transactions: Who, What and Where
Recently we had a scenario where we had a handful of queries being blocked. Nothing unusual there but when I...
2014-01-23 (first published: 2014-01-20)
3,288 reads
The “most_recent_sql_handle” column
While researching my last post I ran across an interesting column I hadn’t noticed before, sys.dm_exec_connections.most_recent_sql_handle. I mentioned it in...
2014-01-22
1,076 reads
Guid vs Identity columns (Ints)
I came across an interesting question on SE last week. Guid vs INT – Which is better as a primary key?...
2014-01-20 (first published: 2014-01-13)
4,682 reads
Blogs
Leading Through Change: Guiding Teams in Times of Uncertainty
By Chris Yates
Change is not a disruption in technology; it is the rhythm. New frameworks appear,...
The Mystery of the Locked-Up Database -Scooby Dooing Episode 6
No Scooby-Doo story is complete without footprints leading to a hidden passage. In SQL...
Announcements from the Microsoft Fabric Community Conference
By James Serra
A bunch of new features for Microsoft Fabric were announced at the Microsoft Fabric Community...
Forums
Don't Forget About Financial Skills
Comments posted to this topic are about the item Don't Forget About Financial Skills
Building a Simple SQL/AI Environment
Comments posted to this topic are about the item Building a Simple SQL/AI Environment
Checking Identities
Comments posted to this topic are about the item Checking Identities
Question of the Day
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')
GO
What is the identity value for the new row inserted by the insert statement above? See possible answers