One of the many new features that have been added to SQL Server 2005 is DDL triggers. We use DML triggers in SQL Server 7.0 and 2000, which executes a bunch of SQL statements or procedures whenever an INSERT, UPDATE or DELETE statement is executed and limited to a table or view object.
2006-02-08
2,440 reads
Trying to find the proverbial needle in the haystack of your SQL Server transactions is no small task. SQL Server Profiler not only helps you find that needle, it gives you details on all the other needles in a single interface.
2006-01-26
2,525 reads
These are not the DMO bits you are thinking of from SQL Server 2000. SQL Server 2005 introduces a new way of digging into the inner workings of the server with both Dynamic Management Views and Dynamic Management Functions. Longtime SQL Server guru Christoffer Hedgate looks at these new ways of understanding your server.
2006-01-26
8,970 reads
Database Snapshot (DB Snapshot for short) is a new tool offered by SQL Server 2005. Database snapshots can be used to protect against user errors, by creating a "snapshot" of your data that you can refer to later if you need to recover data or database objects that were accidentally (or even intentionally) updated or dropped. While the feature is quite useful, it doesn’t provide a 100% guarantee against user errors.
2006-01-24
2,078 reads
This document describes the improved indexed views capability of SQL Server 2005 Enterprise Edition. Indexed views are explained and specific scenarios in which they may provide performance improvements are discussed.
2006-01-19
2,506 reads
2006-01-18
1,896 reads
Definitely written for backup ISVs, but this is an interesting architectural article as to how the backup systems will work in SQL Server 2005.
2006-01-06
2,193 reads
With SQL Server 2005 recently released, one of the things that many people are looking for are some guidelines for working with the new product. New author NandaKishore brings us a list of best practices that should give you a start.
2008-03-14 (first published: 2006-01-04)
121,480 reads
2006-01-03
1,728 reads
Mail processing in SQL Server 2005 has changed substantially, including a new name, DBMail! Corey Bunch birngs is an introduction to this new subsystem, including HTML formatting.
2007-10-02 (first published: 2006-01-03)
68,203 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,...
Comments posted to this topic are about the item Building AI Governance and Policies-...
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...
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