The Database Weekly Update for July 7, 2008
Intel is moving in the direction of more and more cores on a single CPU, so what does that mean for programmers?
Intel is moving in the direction of more and more cores on a single CPU, so what does that mean for programmers?
In the previous installment of our series, we presented a variety of reasons that might influence your decision to upgrade a full-fledged member of the SQL Server 2005 family. This article discusses the actual implementation of this process, pointing out additional factors that might affect its complexity.
Security can be a hassle, but Steve Jones talks about why we sometimes put up with the difficulties of implementing strong security.
Security can be a hassle, but Steve Jones talks about why we sometimes put up with the difficulties of implementing strong security.
Security can be a hassle, but Steve Jones talks about why we sometimes put up with the difficulties of implementing strong security.
Storage area networks (SANs) improve SQL Server performance. Set up SANs on SQL Server with these best practices on migrating to, and configuring SANs.
When do you decide that enough is enough? When does it make sense to let some bugs go and fix them later? Steve Jones comments on the decisions you sometimes make.
When do you decide that enough is enough? When does it make sense to let some bugs go and fix them later? Steve Jones comments on the decisions you sometimes make.
When do you decide that enough is enough? When does it make sense to let some bugs go and fix them later? Steve Jones comments on the decisions you sometimes make.
A blooper collection of mistakes and errors from a variety of editorials on this holiday weekend.
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