SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
03-01-2008, 11:54 AM
| ||||
| ||||
 Fetch Query that triggered the TRIGGER Hello The problem is need to find out the querry that has updated or inserted into the table and in turn 'Triggered the Trigger'. I have the user name, the machine name, Application name, but not the query. The update is not desired and the application is doing it but the application being so large we are unable to pin-point the code which is doing the dammage. Pls help! Regards Anubhav      |
|
03-01-2008, 11:54 AM
| ||||
| ||||
| Re: Fetch Query that triggered the TRIGGER Anubhav (anbansal@gmail.com) writes: > The problem is need to find out the querry that has updated or inserted > into the table and in turn 'Triggered the Trigger'. I have the user > name, the machine name, Application name, but not the query. The update > is not desired and the application is doing it but the application > being so large we are unable to pin-point the code which is doing the > dammage. If the UPDATE is coming directly from a client, you can use dbcc inputbuffer(@@spid) with tableresults but if the error is in a stored procedure, you will not see the UPDATE statement, only the call submitted by the client. -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/pro...ads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinf...ons/books.mspx |
Linear Mode
