Editorial

SQLServerCentral Editorial

Divide and Conquer

  • Editorial

Schemas may be largely irrelevant to small databases, where it is no trouble to assign permissions to individual objects, but they are vital for a hard working corporate database that is being actively developed and used by several applications, with thousands of objects that must be assigned the correct permission.

5 (1)

You rated this post out of 5. Change rating

2014-03-24

207 reads

SQLServerCentral Editorial

Bad Days

  • Editorial

This Friday Steve Jones wants you to look back and cringe a bit. Share with the rest of the community what a bad day was for you and see if it was really as bad as you think.

4 (1)

You rated this post out of 5. Change rating

2018-02-02 (first published: )

241 reads

Blogs

SQL Saturday Boston Slides and Code

By

Thanks to everyone who attended my sessions today at SQL Saturday Boston 2025. I’ve...

Scaling SQL Server 2025 Vector Search with Load-Balanced Ollama Embeddings

By

SQL Server 2025 introduces native support for vector data types and external AI models....

Advice I Like: Fear and Imagination

By

Fear is fueled by a lack of imagination. The antidote to fear is not...

Read the latest Blogs

Forums

How to use data pre-computed in previous ETL SSIS Nodes?

By rafa040500

I'm building ETL packages in SSIS. My data comes from an OLE DB Source...

Building AI Governance and Policies- First Steps

By dbakevlar

Comments posted to this topic are about the item Building AI Governance and Policies-...

Simple delete causes table scan on other tables with foreign key

By askcoffman

Why is sql doing a full scan VS seeking on the index? I've included...

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