External Article

Developing Modifications that Survive Concurrency

You can create a database under the assumption that SQL looks after all the problems of concurrency. It will probably work fine under test conditions: then, in the production environment, it starts losing data in subtle ways that defy repetition. It is every Database Developer's nightmare. In an excerpt from his acclaimed book, Alex Kuznetsov explains why it happens, and how you can avoid such problems.

Blogs

Who Are You Doing It For?

By

But as I've matured over the years, I came to realize that I needed...

Presenting Twice in May 2026

By

I will be presenting my latest session, Documenting Your Work for Worry-Free Vacations, in-person...

Finding the Next Sequence Value: #SQLNewBlogger

By

I saw a question asking about the next sequence value and decided to try...

Read the latest Blogs

Forums

Auto Update Statistics not triggering on filtered indexes

By Leo.Miller

I've got a table with 186,703,969 rows, about 300GB of data. There are several...

What is the difference between SQL Server and SQL Database?

By kamiiteore

I created a SQL Database in Azure Portal but I've just noticed it also...

An Unusual Identity

By Steve Jones - SSC Editor

Comments posted to this topic are about the item An Unusual Identity

Visit the forum

Question of the Day

An Unusual Identity

What values are returned when I run this code?

CREATE TABLE dbo.IdentityTest2
(
     id NUMERIC(10,0) IDENTITY(10,10) PRIMARY KEY,
     somevalue VARCHAR(20)
)
GO
INSERT dbo.IdentityTest2
(
    somevalue
)
VALUES
( 'Steve')
, ('Bill')
GO
SELECT top 10
 id
 FROM dbo.IdentityTest2

See possible answers