A New MVP
Tony Davis offers his congratulations on a new MVP at SQLServerCentral.com and DatabaseWeekly.com.
2008-01-07
51 reads
Articles
Searching Syscomments Accurately
As a SQL Server DBA you should know that your code is stored in syscomments by default. While most DBAs use version control systems, there are times you might want to look through the code on the server for comparison purposes. Robert Cary brings us an article on how you can do this in 2000 and 2005.
2008-01-07 (first published: 2007-01-22)
8,406 reads
Building a Localized Report on a SQL Server 2005 Analysis Service Cube Data Source
Learn how to use an Analysis Services cube as a data source by using parameterized MDX queries, as well as how to localize label strings in a report, in SQL Server 2005.
2008-01-07
2,399 reads
SQL Server 2005 Encryption types
SQL Server 2005 provides four methods of encryption. Part one of this article covers encryption and decryption by passphrase.
2008-01-07
3,647 reads
2008-01-04 (first published: 2003-09-26)
185,320 reads
Predeployment I/O Best Practices
The I/O system is important to the performance of SQL Server. When configuring a new server for SQL Server or when adding or modifying the disk configuration of an existing system, it is good practice to determine the capacity of the I/O subsystem prior to deploying SQL Server. This white paper discusses validating and determining the capacity of an I/O subsystem. A number of tools are available for performing this type of testing. This white paper focuses on the SQLIO.exe tool, but also compares all available tools. It also covers basic I/O configuration best practices for SQL Server 2005.
2008-01-04
3,111 reads
Set Functions: The .AllMembers Function
Business Intelligence Architect Bill Pearson introduces the useful .AllMembers function, reinforcing the basic concepts, as always, with hands-on practice examples.
2008-01-04
2,173 reads
Toward Integrity Part 5
An exploration of the process of translating a conceptual model to a logical model, and ultimately, a faithful implementation using T-SQL.
2008-01-03
2,838 reads
When To Use Cursors
Most SQL Server DBAs have been taught that cursors are bad and should not be used. However there are some cases and places where they might be useful. SQL Server guru Andy Warren brings us an example of where they may be handy.
2008-01-03 (first published: 2007-01-15)
16,896 reads
Introduction to Locking in SQL Server
Locking is a major part of every RDBMS and is important to know about. It is a database functionality which without a multi-user environment could not work. The main problem of locking is that in an essence it's a logical and not physical problem. This means that no amount of hardware will help you in the end. Yes you might cut execution times but this is only a virtual fix.
2008-01-03
4,767 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