IT Project Euthanasia
A guest editorial from Phil Factor on the kindest way to dispose of unwanted IT projects.
New Features in Reporting Services 2005
Reporting is one of the key parts of any data warehouse or business intelligence systems. Vincent Rainardi has brought us some great information on data warehousing and now turns his attention to some of the very useful new features in Reporting Services 2005.
Policy-based Management in SQL Server 2008 – Part II
Learn how to use SQL Server Agent alerts and jobs to fix policy incompliance automatically.
SQL Code Layout and Beautification
William Brewer takes a look at the whole topic of SQL Code layout and beautification, an important aspect to SQL programming style. He concludes that once you are tired of laying SQL out by hand, you had better choose a tool with plenty of knobs to twiddle, because nobody seems to agree on the best way of doing it.
SQLServerCentral Friday Crossword No 2
Pit your wits against the SQLServerCentral.com Friday crossword...
The Hazards of IT
Are you taking care of yourself as an IT professional? We try to cover all aspects of your SQL Server career here, not just the technical stuff. Longtime SQL Server guru Michael Coles brings us some health tips in an interview with Dr. Jerry Sanders
Upgrading SQL Server 2000 DTS Packages to SSIS
If you're like Brian Knight, you probably have dozens if not hundreds of DTS packages running around that you're terrified to touch. SQL Server 2005 has some interesting methods to upgrade your packages to SSIS with minimal effort. This article shows you a few ways that you can use to upgrade and some of the drawbacks.
Database Audit Logs, Joel on Software, Code Handouts, and More
Database systems like Microsoft® SQL Server® have long supported triggers—developer-created scripts that automatically execute after or in place of INSERT, UPDATE, and DELETE statements. Because triggers can access the data modified by INSERT, UPDATE, or DELETE, they are an excellent tool for recording data changes to an audit log.
Blogs
Advice I Like: Fear and Imagination
By Steve Jones
Fear is fueled by a lack of imagination. The antidote to fear is not...
Cloud Data Driven User Group 2025 – Slides & Scripts
The slidedeck and the SQL scripts for the session Indexing for Dummies can be...
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,...
Forums
How to use data pre-computed in previous ETL SSIS Nodes?
I'm building ETL packages in SSIS. My data comes from an OLE DB Source...
Building AI Governance and Policies- First Steps
Comments posted to this topic are about the item Building AI Governance and Policies-...
Simple delete causes table scan on other tables with foreign key
Why is sql doing a full scan VS seeking on the index? I've included...
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