2007-10-22
4,167 reads
2007-10-22
4,167 reads
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
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
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)
48,046 reads
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
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,285 reads
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,325 reads
In this article by Robert Marda, he shows you how to setup a simple auditing system through triggers.
2004-01-16
16,779 reads
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,694 reads
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,281 reads
By Steve Jones
semaphorism – n. a conversational hint that you have something personal to say on...
This week I was at PASS Data Community Summit in Seattle, and I attended...
By James Serra
(This is the third post in a three-part series on how AI is changing...
Comments posted to this topic are about the item Pay for Performance, which is...
Comments posted to this topic are about the item Helping an English Student with...
I have a table, dbo.bittest, where I am testing an application response. This has this structure:
CREATE TABLE [dbo].[BitTest] ( [insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()), [a] [bit] NULL ) ON [PRIMARY] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, 'true')
GO
See possible answers