Myths - WMV
Every profession has its share of myths about how it works. IT might have more than its share and Steve Jones comments on a few of them.
2008-01-09
52 reads
Articles
Test Data Generation with Data Dude
The Visual Studio 2005 Team Edition for Database Professionals (a.k.a Data Dude) was released somewhere around December 2006 helping many Database Administrators and Database Developers. The release was huge for us, because it addresses many issues faced by us.
2008-01-09
3,641 reads
The Backup Myth - WMV
Running backups is enough for disaster recovery, right? That's a myth that could get you into trouble. Steve Jones explains there's more that's needed.
2008-01-09
305 reads
First Look: SQL Server 2005 SP2 CTP
Service Pack 2 for SQL Server 2005 is not quite here, but Wayne Fillis brings us a look at what you can expect if you install the CTP version that is available now.
2008-01-08 (first published: 2007-01-09)
11,444 reads
Partitioning - Part 3
Continuing on with his series on SQL Server table partitioning, Andy Warren takes a look at how partitioned views are handled when you query them.
2008-01-08
8,252 reads
Disk Space Usage and SQL Server Performance
Every extra byte of space you waste in your database causes a performance hit to your application. This article looks at disk space usage and how it affects performance.
2008-01-08
7,011 reads
Measure TSQL Statement Performance
Every developer needs to ensure that each TSQL statement is optimized. This article will give you a few different ideas on how to identify slow running queries and provide you with some tips on monitor your query performance while you make iterative changes to each query to try and improve performance.
2008-01-08
4,445 reads
The Backup Myth (iPod)
Running backups is enough for disaster recovery, right? That's a myth that could get you into trouble. Steve Jones explains there's more that's needed.
2008-01-08
317 reads
The Backup Myth (MP3)
Running backups is enough for disaster recovery, right? That's a myth that could get you into trouble. Steve Jones explains there's more that's needed.
2008-01-08
641 reads
The Backup Myth (WMV)
Running backups is enough for disaster recovery, right? That's a myth that could get you into trouble. Steve Jones explains there's more that's needed.
2008-01-08
296 reads
Blogs
Leading Through Change: Guiding Teams in Times of Uncertainty
By Chris Yates
Change is not a disruption in technology; it is the rhythm. New frameworks appear,...
The Mystery of the Locked-Up Database -Scooby Dooing Episode 6
No Scooby-Doo story is complete without footprints leading to a hidden passage. In SQL...
Announcements from the Microsoft Fabric Community Conference
By James Serra
A bunch of new features for Microsoft Fabric were announced at the Microsoft Fabric Community...
Forums
Don't Forget About Financial Skills
Comments posted to this topic are about the item Don't Forget About Financial Skills
Building a Simple SQL/AI Environment
Comments posted to this topic are about the item Building a Simple SQL/AI Environment
Checking Identities
Comments posted to this topic are about the item Checking Identities
Question of the Day
Checking Identities
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