Articles

SQLServerCentral Article

Finding Primes

While it's not likely that many of you need to find prime numbers using T-SQL, it is an interesting programming exercise. SQL Server guru Kathi Kellenburger brings us one solution after taking a break over the holidays and reading some popular fiction.

4.33 (6)

You rated this post out of 5. Change rating

2008-01-01 (first published: )

7,375 reads

SQLServerCentral Article

The Dynamic Process of Loading Data

When loading a data warehouse, handling the ETL process of working with files can be problematic. Longtime DBA Janet Wong brings us an interesting solution that is flexible and efficient for quickly loading a number of files into a warehouse using DTS.

3.13 (8)

You rated this post out of 5. Change rating

2007-12-31 (first published: )

9,948 reads

Blogs

Leading Through Change: Guiding Teams in Times of Uncertainty

By

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

By

No Scooby-Doo story is complete without footprints leading to a hidden passage. In SQL...

Announcements from the Microsoft Fabric Community Conference

By

A bunch of new features for Microsoft Fabric were announced at the Microsoft Fabric Community...

Read the latest Blogs

Forums

Checking Identities

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Checking Identities

Compatibility levels on database changing them and impacts.

By jonluder

We’re running SQL Server 2019 with database compatibility level 150, and after recent tuning...

Changing the Recovery Time

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changing the Recovery Time

Visit the forum

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-16
The 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