﻿<?xml version="1.0" encoding="utf-8"?><rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="2.0"><channel><title>SQLServerCentral.com Content tagged Triggers</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Triggers posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Set trigger firing order</title><guid>http://www.sqlservercentral.com/questions/Triggers/62673/</guid><pubDate>2008/04/29</pubDate><link>http://www.sqlservercentral.com/questions/Triggers/62673/</link></item><item><title>Row-By-Row Processing Without Cursor</title><description>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.

</description><guid>http://www.sqlservercentral.com/articles/Triggers/2747/</guid><pubDate>2007/12/28</pubDate><link>http://www.sqlservercentral.com/articles/Triggers/2747/</link></item><item><title>DML Triggers</title><guid>http://www.sqlservercentral.com/questions/Triggers/61589/</guid><pubDate>2007/12/12</pubDate><link>http://www.sqlservercentral.com/questions/Triggers/61589/</link></item><item><title>Row-By-Row Processing Without Cursor</title><description>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.

</description><guid>http://www.sqlservercentral.com/articles/Triggers/2747/</guid><pubDate>2007/12/28</pubDate><link>http://www.sqlservercentral.com/articles/Triggers/2747/</link></item><item><title>Trigger Trivia</title><description>From SQL Server trainer and guru Andy Warren, he are a few short nuggets that you might not realize about triggers.</description><guid>http://www.sqlservercentral.com/articles/T-SQL/61483/</guid><pubDate>2007/11/13</pubDate><link>http://www.sqlservercentral.com/articles/T-SQL/61483/</link></item><item><title>Checking a Trigger</title><guid>http://www.sqlservercentral.com/questions/Triggers/61354/</guid><pubDate>2007/10/22</pubDate><link>http://www.sqlservercentral.com/questions/Triggers/61354/</link></item><item><title>Row-By-Row Processing Without Cursor</title><description>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.

</description><guid>http://www.sqlservercentral.com/articles/Triggers/2747/</guid><pubDate>2007/12/28</pubDate><link>http://www.sqlservercentral.com/articles/Triggers/2747/</link></item><item><title>Using DDL Database Triggers</title><description>In this short demonstration, you&amp;#39;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.
</description><guid>http://www.sqlservercentral.com/redirect/articles/2509/</guid><pubDate>2006/07/20</pubDate><link>http://www.sqlservercentral.com/redirect/articles/2509/</link></item><item><title>Stored Procedure vs Triggers</title><description>Performance tuning is an ongoing battle in SQL Server, but having a little knowledge up front when designing an application can greatly reduce the efforts. Do you know which performs better: stored procedures or triggers? There aren&amp;#39;t many places where the two are interchangeable, but knowing the impacts of each might change the way you build an application. Read about this analysis by Vijaya Kumar.


</description><guid>http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/storedprocedurevstriggers/1449/</guid><pubDate>2006/03/31</pubDate><link>http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/storedprocedurevstriggers/1449/</link></item><item><title>Triggers for Auditing</title><description>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.
</description><guid>http://www.sqlservercentral.com/articles/Triggers/triggersforauditing/2143/</guid><pubDate>2005/11/29</pubDate><link>http://www.sqlservercentral.com/articles/Triggers/triggersforauditing/2143/</link></item><item><title>Triggers in SQL Server 7.0 and 2000 - What's New</title><description>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&amp;#39;s been added to SQL Server 2000.


</description><guid>http://www.sqlservercentral.com/articles/Triggers/triggersinsqlserver7.0and2000-what'snew/431/</guid><pubDate>2005/06/24</pubDate><link>http://www.sqlservercentral.com/articles/Triggers/triggersinsqlserver7.0and2000-what'snew/431/</link></item><item><title>Triggers in SQL Server 7.0 and 2000 - The Common Ground</title><description>This is a two part series on how triggers work in the two latest versions of MS SQL Server.  Because there are some pretty significant additions in trigger functionality from 7.0 to 2000, we&amp;#39;ll first need to look at what the two versions have in common.  The second part to this series will look at the differences between the two MS SQL Server versions.


</description><guid>http://www.sqlservercentral.com/articles/Triggers/triggers_1/389/</guid><pubDate>2005/01/21</pubDate><link>http://www.sqlservercentral.com/articles/Triggers/triggers_1/389/</link></item><item><title>Stored Procedure vs Triggers</title><description>Performance tuning is an ongoing battle in SQL Server, but having a little knowledge up front when designing an application can greatly reduce the efforts. Do you know which performs better: stored procedures or triggers? There aren&amp;#39;t many places where the two are interchangeable, but knowing the impacts of each might change the way you build an application. Read about this analysis by Vijaya Kumar.


</description><guid>http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/storedprocedurevstriggers/1449/</guid><pubDate>2006/03/31</pubDate><link>http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/storedprocedurevstriggers/1449/</link></item><item><title>Worst Practice - Triggering External Events</title><description>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.

</description><guid>http://www.sqlservercentral.com/articles/Triggers/worstpracticetriggeringexternalevents/1283/</guid><pubDate>2004/02/23</pubDate><link>http://www.sqlservercentral.com/articles/Triggers/worstpracticetriggeringexternalevents/1283/</link></item><item><title>Auditing Through Triggers</title><description>In this article by Robert Marda, he shows you how to setup a simple auditing system through triggers.


</description><guid>http://www.sqlservercentral.com/articles/Triggers/auditingtriggers/579/</guid><pubDate>2004/01/16</pubDate><link>http://www.sqlservercentral.com/articles/Triggers/auditingtriggers/579/</link></item><item><title>Bypassing Triggers</title><description>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!

</description><guid>http://www.sqlservercentral.com/articles/Triggers/bypassingtriggers/1177/</guid><pubDate>2003/11/24</pubDate><link>http://www.sqlservercentral.com/articles/Triggers/bypassingtriggers/1177/</link></item><item><title>Testing for an Updated Column in a Trigger</title><description>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!

</description><guid>http://www.sqlservercentral.com/articles/Triggers/triggerscolumnsupdated/115/</guid><pubDate>2003/08/21</pubDate><link>http://www.sqlservercentral.com/articles/Triggers/triggerscolumnsupdated/115/</link></item><item><title>Review of SQL 2000 Fast Answers</title><description>A monster book at 980 pages, it&amp;#39;s written in &amp;#39;how-to&amp;#39; format and has a ton of good material. Andy gave it the once over for us and reports back - see what he thinks!

</description><guid>http://www.sqlservercentral.com/articles/Installation/reviewofsql2000fastanswers/959/</guid><pubDate>2003/04/18</pubDate><link>http://www.sqlservercentral.com/articles/Installation/reviewofsql2000fastanswers/959/</link></item><item><title>Creating your own sp_MSforeach stored procedure</title><description>This article shows you one of the most time saving stored procedure built into SQL Server and then shows you how you can modify it to affect additional objects like triggers. For example, after this article and the code in the article, you&amp;#39;ll be able to disable every trigger in your system in one line of code.
</description><guid>http://www.sqlservercentral.com/articles/Administering/sp_msforeachworker/711/</guid><pubDate>2002/06/17</pubDate><link>http://www.sqlservercentral.com/articles/Administering/sp_msforeachworker/711/</link></item><item><title>Review of SQL Server 2000 Programming (MSPress)</title><description>Andy sits down with an entry level book to see if he should use it at work as a teaching aid. Did he like it? Should you buy it? Read the review now!

</description><guid>http://www.sqlservercentral.com/articles/Installation/reviewofsqlserver2000programmingmspress/694/</guid><pubDate>2002/06/04</pubDate><link>http://www.sqlservercentral.com/articles/Installation/reviewofsqlserver2000programmingmspress/694/</link></item><item><title>Triggers in SQL Server 7.0 and 2000 - What's New</title><description>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&amp;#39;s been added to SQL Server 2000.


</description><guid>http://www.sqlservercentral.com/articles/Triggers/triggersinsqlserver7.0and2000-what'snew/431/</guid><pubDate>2005/06/24</pubDate><link>http://www.sqlservercentral.com/articles/Triggers/triggersinsqlserver7.0and2000-what'snew/431/</link></item><item><title>Triggers in SQL Server 7.0 and 2000 - The Common Ground</title><description>This is a two part series on how triggers work in the two latest versions of MS SQL Server.  Because there are some pretty significant additions in trigger functionality from 7.0 to 2000, we&amp;#39;ll first need to look at what the two versions have in common.  The second part to this series will look at the differences between the two MS SQL Server versions.


</description><guid>http://www.sqlservercentral.com/articles/Triggers/triggers_1/389/</guid><pubDate>2005/01/21</pubDate><link>http://www.sqlservercentral.com/articles/Triggers/triggers_1/389/</link></item><item><title>SQL Server 2000: .NET and the Death and Re-Birth o</title><description>In this month&amp;#39;s article I will cover an aspect of SQL Server that always generates a great deal of, well, shall we say &amp;#34;discussion&amp;#34;—triggers. Love them or hate them, SQL Server 2000 will change they way you think about triggers and will probably alter the way you design your applications. Specifically, this month I will dive into cascading referential integrity (RI) and the new INSTEAD OF and AFTER trigger concepts in SQL Server 2000. 
</description><guid>http://www.sqlservercentral.com/redirect/articles/253/</guid><pubDate>2001/07/27</pubDate><link>http://www.sqlservercentral.com/redirect/articles/253/</link></item></channel></rss>