2006-11-01
1,254 reads
2006-11-01
1,254 reads
2006-10-27
1,543 reads
2006-10-23
1,613 reads
Learn how to make life easier by dividing large tables and indexes into smaller parts.
2006-10-23
3,774 reads
It's small and neat but it might just save your data...Robyn Page's crib sheet tells you everything you wanted to know about SQL Server backup but were afraid to ask.
2006-10-20
4,868 reads
The .NET Framework 2.0 and Visual Studio 2005 make it easy to create a basic but extensible database-monitoring solution without a lot of complexity or coding.
2006-10-18
4,043 reads
Microsoft has come to the rescue for managing large text fields in SQL Server 2005, by creating a few new large value data types. This article explores these new data types.
2006-10-09
2,297 reads
2006-10-02
1,035 reads
Most DBAs manage multiple SQL servers, each handling different needs for your business. Even with the diverse uses for different servers, there is often the need to deploy the same scripts to all servers for various purposes. Author Joe Doherty brings us his scripts and technique for executing a script across multiple servers.
2006-09-27
9,909 reads
Most SQL Server instances are installed with the default values, but that's not always the way it should be. Often there is the need to "move" databases to comply with standards, free up disk space, or some other reason. Moving the system databases can be a little tricky, but author Vince Iacoboni brings us his code and technique for easily doing this for SQL Server 2005 databases.
2007-09-28 (first published: 2006-09-26)
35,760 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