2009-03-11
6,341 reads
2009-03-11
6,341 reads
Handling the paging of results in T-SQL has been a challenge for a long time. Robert Cary presents an interesting technique in this article.
2010-05-08 (first published: 2009-03-11)
41,797 reads
2009-03-06
4,324 reads
2009-03-04
4,043 reads
Deleting all the data in a SQL Server database doesn't have to involve complex code. The undocumented stored procedure sp_MSForEachTable safely bypasses built-in limitations to accomplish this common task.
2009-03-03
4,786 reads
2009-03-02
4,291 reads
Sixth in a series of scripts demonstrating a quantitative comparison between the text of two stored procedures
2009-04-15 (first published: 2009-02-26)
1,399 reads
Fifth in a series of scripts demonstrating a quantitative comparison between the text of two stored procedures
2009-04-03 (first published: 2009-02-23)
1,404 reads
In which Phil illustrates an old trick using STUFF to intert a number of substrings from a table into a string, and explains why the technique might speed up your code...
2009-02-18
1,631 reads
Fourth in a series of scripts demonstrating a quantitative comparison between the text of two stored procedures
2013-10-31 (first published: 2009-02-17)
10,567 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