In-Memory OLTP and the Identity Column
Over the past month I've been playing around with the new In-Memory OLTP (code name: "Hekaton") features within SQL Server...
2013-11-12
1,505 reads
Over the past month I've been playing around with the new In-Memory OLTP (code name: "Hekaton") features within SQL Server...
2013-11-12
1,505 reads
The host for T-SQL Tuesday #47 is Kendal Van Dyke (blog|twitter), and his topic of choice is about the best...
2013-10-08
950 reads
Wow! It’s been one year since I launched my blog, and my how things have changed.
Accomplishments Over the Past...
2013-09-24
690 reads
As a DBA, we're often asked to troubleshoot performance issues for stored procedures. One of the most common tools at...
2013-09-06 (first published: 2013-09-03)
3,257 reads
You've spent a lot of time planning and building out a new SQL Server 2012 environment complete with Availability Group...
2013-08-29 (first published: 2013-08-27)
2,393 reads
I know what y'all are thinkin', what's Charlotte got to do with SQL Server? Just hear me out. There's a...
2013-08-20
1,277 reads
UPDATED -- Jul 3, 2015 -- To verify database exists, per comments by Konstantinos Katsoridis. Thanks for finding the bug!
In my recent adventures...
2013-07-23
1,640 reads
Before we get started, I want to make it clear this is NOT how you would normally configure all these...
2013-07-16
2,510 reads
Industry experts will tell you that virtualization of your environment is not done to improve performance, it's done to make...
2013-06-25
4,417 reads
SQL Server includes a DMV, sys.dm_exec_query_stats, that returns performance statistics for each query plan cached in memory. However, it can...
2013-05-28
1,134 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