In SQL Server 2005, object ownership will have a different meaning, but since most of us work with SQL Server 2000, Kathi Kellenberger has written a good introduction to understanding how object ownership works and why you might want to follow certain practices.
2007-10-02 (first published: 2005-07-18)
54,857 reads
I work almost exclusively with third party applications. I don't get to do a lot of tuning except for reports...
2007-09-30
1,289 reads
We are trying to move to version 2 of our accounting data warehouse (more likely called a datamart), but it...
2007-09-25
1,595 reads
When I first got into IT full time 10 years ago, I noticed that my mind was constantly solving programming...
2007-09-25
1,267 reads
Somehow between the sessions, networking and socializing I never found time to post anything last week. So, I'm going to...
2007-09-23
1,326 reads
This was my 5th year at PASS and every year I enjoy catching up with old friends and meeting many...
2007-09-23
1,354 reads
SQL Server 2000 is the basis for the new Access database storage. However there are still many cases where applications developed on Access are outgrown and need to be moved to SQL Server to support the load. Author Kathi Kellenberger brings us a look at the Upsizing Wizard and how you can move your databases to SQL Server.
2007-09-22 (first published: 2005-02-22)
30,764 reads
I haven't posted much lately, but it has been a busy few months with many family activities. At work, I...
2007-07-09
433 reads
I was at DevTeach/SQLTeach in Montreal last week. The conference was very well run and the organizers did a great...
2007-05-19
1,305 reads
Yesterday's post reminded me of another interesting technique I have used to change the color of the values on a...
2007-03-11
1,318 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