DDL Triggers in SQL Server 2005
DDL Triggers are key improvement in SQL Server auditing, allowing tracking of events such as the creation of a new table, database or user.
2007-09-24
2,739 reads
Triggers
Using DDL Triggers in SQL Server 2005 to Capture Schema Changes
This article shows how to use DDL triggers to capture schema changes. This solutions works a little differently than most DDL triggers examples. This script captures the old object that was replaced.
2007-08-28
2,785 reads
Row-By-Row Processing Without Cursor
If you are a SQL Server DBA, you realize that the performance of cursors is not great and they should be avoided where possible. One place it is difficult to avoid cursors is individual row processing within a trigger. Amin Sobati brings us a new article that shows just how you can avoid this.
2007-12-28 (first published: 2006-12-07)
47,970 reads
Using DDL Database Triggers
In this short demonstration, you'll learn how to use DDL database triggers to prevent changes to product and audit changes to comply with Sarbanes-Oxley and other change management requirements. Free registration required.
2006-07-20
3,395 reads
Triggers for Auditing
Have you ever needed to audit your SQL Server 2000 database for changes to a table? A simple auditing solution is presented here by new author Tiago Silva using an INSTEAD OF trigger.
2005-11-29
12,240 reads
Worst Practice - Triggering External Events
Andy Warren started his worst practice series some time ago with the intention of looking at the worst things you can do. Given that we may not always be able to implement the best practices, at least we can try to avoid doing things harm the system or decrease performance. This article continues the series and looks at an item I see mentioned in our discussion forum quite often, triggering external events. From a trigger.
2004-02-23
10,258 reads
Auditing Through Triggers
In this article by Robert Marda, he shows you how to setup a simple auditing system through triggers.
2004-01-16
16,729 reads
Bypassing Triggers
This articles covers a variety of techniques to let you bypass or conditionally execute code in a trigger based on criteria outside of the inserted/deleted tables. It also includes a contest that gives you a chance to win a copy of our book The Best of SQLServerCentral.com 2002!
2003-11-24
12,596 reads
Testing for an Updated Column in a Trigger
The columns_updated function gives you the ability to easily test to see if specific columns were modified with less code than you might otherwise need to use. In this article Andy Warren demonstrates how to create a trigger that uses this function and points out some reasons why you may NOT want to use it!
2003-08-21
18,239 reads
Triggers in SQL Server 7.0 and 2000 - What's New
This is the second of a two part series on how triggers work in the two latest versions of MS SQL Server. The first part dealt with what is common between the two versions. This article will detail what's been added to SQL Server 2000.
2005-06-24 (first published: 2001-09-03)
72,983 reads
Blogs
TempDB Internals – What’s New (SQL Server 2016 to 2022)
By Vinay Thakur
I wrote about TempDB Internals and understand that Tempdb plays very important role on...
AI: Blog a Day – Day 2: Generative AI, Multimodal Systems, and Agent AI
By Vinay Thakur
continuing from Day 1 where we covered the history of AI and GPT family,...
Forums
A Quick Restore
Comments posted to this topic are about the item A Quick Restore
Guarding Against SQL Injection at the Database Layer (SQL Server)
Comments posted to this topic are about the item Guarding Against SQL Injection at...
Ola Hallengren Index Optimize Maintenance can we have data compression = page
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
Question of the Day
A Quick Restore
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers