In the final installment of this three-Level series, we use another automation-related feature to do what SSDT doesn't handle natively.
2022-06-01 (first published: 2016-03-03)
6,622 reads
(last updated: 2021-09-01 @ 14:18 ET / 2021-09-01 @ 18:18 UTC ) In my previous post, SSMS and SQLCMD: Prevent T-SQL Batch From Not Only Executing, but Also From...
2021-08-31
92 reads
(last updated: 2021-08-13 @ 19:50 ET / 2021-08-13 @ 23:50 UTC ) In a previous post, Prevent Full Script Execution (Understanding and Using PARSEONLY and NOEXEC), I explained how...
2021-08-25 (first published: 2021-08-13)
520 reads
(last updated: 2021-07-02 @ 19:55 EST / 2021-07-02 @ 23:55 UTC ) The sysname data type (in SQL Server) is a system-provided, though not built-in, alias for NVARCHAR(128). This...
2021-07-02
120 reads
(last updated: 2021-05-31 @ 19:00 EST / 2021-05-31 @ 23:00 UTC ) Many of us that work with Microsoft SQL Server, especially those of us working on systems with...
2021-05-21
145 reads
This time we look at the commonly used tools for doing SQLCLR development: Visual Studio (VS), SQL Server Data Tools (SSDT), and SQL Server Express LocalDB (LocalDB).
2021-03-10 (first published: 2016-03-01)
6,384 reads
In the second level of our Stairway to SQLCLR, we look at how to enable the SQLCLR in SQL Server. We then build an assembly, store procedure, and a function that can be called from your T-SQL code.
2020-07-09 (first published: 2019-09-24)
27,098 reads
Presenting about Module Signing at "Data Architecture Day" this Saturday (May 16th) at 4:10 PM EDT… Continue reading Presenting at “Data Architecture Day” this Saturday (May 16th) at 4:10...
2020-05-14
30 reads
Is EXISTS(SELECT 1 ...) better than EXISTS(SELECT * ...)? Who would know better than SQL Server?… Continue reading Actual Difference Between EXISTS(SELECT 1 …), EXISTS(SELECT * …), and EXISTS(SELECT...
2020-02-03 (first published: 2020-01-24)
3,206 reads
sys.xp_delete_files and 'allow filesystem enumeration': two new undocumented items in SQL Server 2019… Continue reading sys.xp_delete_files and ‘allow filesystem enumeration’: two new undocumented items in SQL Server 2019 ?
2020-01-27
568 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')
GO
What is the identity value for the new row inserted by the insert statement above? See possible answers