﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2005 / SQL Server 2005 General Discussion  / Simple Trigger causing deadlock problem / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sat, 18 May 2013 15:39:18 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Simple Trigger causing deadlock problem</title><link>http://www.sqlservercentral.com/Forums/Topic1419485-149-1.aspx</link><description>ok i see the pointi'll try to convince the customer...</description><pubDate>Wed, 13 Feb 2013 08:39:42 GMT</pubDate><dc:creator>marc 11239</dc:creator></item><item><title>RE: Simple Trigger causing deadlock problem</title><link>http://www.sqlservercentral.com/Forums/Topic1419485-149-1.aspx</link><description>Enabling a Trace Flag is not the same as running a Trace. If you do not have a deadlock graph and you cannot enable the Trace Flag and the trigger to attain one the next time this happens then it is going to be hard, if not impossible, to help you.Clustering does not have any effect on deadlock issues. Deadlocks occur for many reasons and the root cause of some scenarios can be quite difficult to determine, especially without a deadlock graph.</description><pubDate>Wed, 13 Feb 2013 08:35:25 GMT</pubDate><dc:creator>opc.three</dc:creator></item><item><title>RE: Simple Trigger causing deadlock problem</title><link>http://www.sqlservercentral.com/Forums/Topic1419485-149-1.aspx</link><description>the only other thing worth mentioning is that it is a clustered server...</description><pubDate>Wed, 13 Feb 2013 08:28:07 GMT</pubDate><dc:creator>marc 11239</dc:creator></item><item><title>RE: Simple Trigger causing deadlock problem</title><link>http://www.sqlservercentral.com/Forums/Topic1419485-149-1.aspx</link><description>no i can't...i got the error during havy load but also when there were only 10 recs inserted...so no trace is running at this momentand i can't turn the trigger on at this point when the system is under heavy load cause they don't want instabilityso this limits my options....i could turn it on now but i can't simulate the problem...thx</description><pubDate>Wed, 13 Feb 2013 08:26:26 GMT</pubDate><dc:creator>marc 11239</dc:creator></item><item><title>RE: Simple Trigger causing deadlock problem</title><link>http://www.sqlservercentral.com/Forums/Topic1419485-149-1.aspx</link><description>Can you post the deadlock graph?If you do not already have one captured enable trace flag 1222 and then one occurs again you can retrieve it from the SQL Error Log.</description><pubDate>Wed, 13 Feb 2013 08:21:38 GMT</pubDate><dc:creator>opc.three</dc:creator></item><item><title>Simple Trigger causing deadlock problem</title><link>http://www.sqlservercentral.com/Forums/Topic1419485-149-1.aspx</link><description>hi,i have 3 databases in the same sql 2005 serverdb1 and db2 hold both a table A in which only rows get inserted, never deleted nor updatedi needed to combine both so i created db3 with the same table A' and with an extra column identifying the originsince i wanted the events to be inserted in real time i created a trigger on both db1.A and db2.Acreate trigger on db1.Aafter insertset nocount on insert into db3.A' (origigin, fields...) select 1,INSERTED.fields... from insertedsame trigger on db2.Anow this works rather well but sometimes throws a deadlockand i have no clue why it should...any ideas/suggestions?tia,marc</description><pubDate>Wed, 13 Feb 2013 06:55:44 GMT</pubDate><dc:creator>marc 11239</dc:creator></item></channel></rss>