Clustered Index Uniquifier Existence and Size
In SQL Server, each and every row in a table needs to be accessible by itself, whether or not you...
2017-09-19
1,901 reads
In SQL Server, each and every row in a table needs to be accessible by itself, whether or not you...
2017-09-19
1,901 reads
In the previous post in this series on SQLCLR in SQL Server 2017 — Part 4: “Trusted Assemblies” — The Disappointment — we...
2017-09-04
410 reads
Recap
Before we look at “Trusted Assemblies”, let’s take a moment to review the context of the situation. First, the “Good”:...
2017-08-28
1,306 reads
Welcome back, everyone. In the previous post in this series, I explained how to work within the new SQLCLR security...
2017-08-16
702 reads
As mentioned in Part 1 of this “SQLCLR vs. SQL Server 2017” series, the new clr strict security server-level configuration...
2017-08-09
955 reads
The Good, the Bad, and the Ugle¯e¯ (need to avoid copyright infringement ?? )
SQL Server 2017 is soon to be officially...
2017-08-07
2,341 reads
In SQL Server Management Studio (SSMS), there are a lot of options and functions. In fact, there are so many...
2017-07-20
2,062 reads
SQL Server Management Studio (SSMS) for SQL Server 2016 added some interesting enhancements for the vertical scroll bar: Map Mode...
2017-07-17
637 reads
Quite often people will use, or will recommend using, a binary Collation (one ending in “_BIN” or “_BIN2“) when wanting...
2017-07-13
2,118 reads
You may have heard, or read, that you should not mix VARCHAR and NVARCHAR datatypes, especially when one of them...
2017-07-10
5,071 reads
By Steve Jones
Thanks to everyone who attended my sessions today at SQL Saturday Boston 2025. I’ve...
SQL Server 2025 introduces native support for vector data types and external AI models....
By Steve Jones
Fear is fueled by a lack of imagination. The antidote to fear is not...
I'm building ETL packages in SSIS. My data comes from an OLE DB Source...
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...
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