2006-06-23
1,244 reads
2006-06-23
1,244 reads
Automating the installation of SQL Server was made simple in SQL Server 2005. SQL Server 2005 can be installed using a GUI, an ini file or just run setup.exe with a bunch of parameters.
2006-06-19
2,304 reads
2006-06-16
1,672 reads
The Database Tuning Advisor (DTA) is an improvement over the old Index Tuning Wizard. Learn how to access the advanced features of DTA from the command line with a custom configuration.
2006-06-13
1,777 reads
2006-06-09
1,498 reads
2006-06-06
1,396 reads
As everyone moves to SQL Server 2005 from SQL Server 2000, there are quite a few pieces of information that have moved and may give you trouble finding. Boris Balinger brings us a followup to his first look at some of those changes with a quick article on how you can get the free space in your database files.
2006-06-06
9,345 reads
2006-06-02
1,661 reads
2006-06-01
1,441 reads
2006-05-30
1,275 reads
By Steve Jones
Fear is fueled by a lack of imagination. The antidote to fear is not...
The slidedeck and the SQL scripts for the session Indexing for Dummies can be...
By Chris Yates
Change is not a disruption in technology; it is the rhythm. New frameworks appear,...
Why is sql doing a full scan VS seeking on the index? I've included...
We have a report that has multiple tables that list the top 15 performers...
We have a tool called DB Moto that reads journals (like t-logs) and replicates...
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