Steve Jones wonders about the next generations of IT workers. Can we encourage more people to enter this field? With the supposed shortages of talent today and the poor reputation of IT positions, can we change the trend of fewer people entering IT?
2014-08-15
182 reads
How much would you pay for a laugh? Maybe you'll donate to ensure that some of your SQL Server speakers will embarrass themselves at the PASS Summit.
2014-08-14
240 reads
Can a single piece of software work well for most situations? Steve Jones wonders if we're not attacking the problems of large software applications in the right way.
2014-08-13
156 reads
Replication is a great feature in SQL Server, but it seems brittle. When things go wrong, they break quickly, and often severely. It seems that we have many features like this in SQL Server that are useful and handy, but receive very little attention as versions are released.
2014-08-12
235 reads
Most of us say we care about IT and data security. Our actions speak differently.
2014-08-11
539 reads
More data is better, but Steve Jones notes that even that isn't always enough to make decisions count for your organization.
2014-08-11
100 reads
2014-08-08
260 reads
2014-08-06
683 reads
Mistakes happen but how can we minimize them and deal with them whey they do happen?
2014-08-05
213 reads
In opera, tragedy or absurdity happens because the characters are incapable of standing back, and making a difficult decision. Instead, at every stage, they just drift towards their fate by taking the easy option. Don't let the same fate befall you, as a DBA.
2014-08-04
107 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