Finding out what happened on a SQL Server instance can be a challenge for even experienced DBAs. SQLClue, a new tool by longtime SQL Server expert Bill Wunder can help. We have a short case study that shows you how this tool can help.
2009-02-23
2,996 reads
Longtime SQL Server expert Bill Wunder has written a very interesting article on how to share knowledge among IT staff using the tools you already have in your organization.
2008-08-06
6,716 reads
If your shop is even close to the typical Microsoft SQL Server environment there are several people that can make changes to the production environment and what's in SourceSafe does not match what's on the SQL Server. This freeware by Bill Wunder will make archiving DDL and DTS packages a piece of cake and simplify deployment of SQL Server code. Available exclusivily for SQLServerCentral.com members.
2003-07-17
819 reads
Bill Wunder has done it again with his newest release of his DDL Archive Utility, which can pull entire schemas into Source Safe automatically.
2002-08-13
203 reads
Bill Wunder has donated his utility for those who have a free SQLServerCentral.com mebership. The DDL Archive Utility will look into a database and automatically archive the DDL from the database into Source Safe saving hours of hassles!
2002-07-11
239 reads
2001-06-14
5,607 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')
GO
What is the identity value for the new row inserted by the insert statement above? See possible answers