﻿<?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, T-SQL</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Triggers, T-SQL posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Comparing SQL Server constraints and DML triggers</title><description>Over the years, I have witnessed many developers being confused about when to use data-manipulation language (DML) triggers vs. when to use constraints.</description><guid>http://www.sqlservercentral.com/redirect/articles/63705/</guid><pubDate>2008/07/23</pubDate><link>http://www.sqlservercentral.com/redirect/articles/63705/</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>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>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>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>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>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></channel></rss>