Re: Cursor in a trigger
From: Jacco Schalkwijk (NOSPAMjaccos_at_eurostop.co.uk)
Date: 02/25/04
- Next message: Dan Guzman: "Re: Procedure parameters from select"
- Previous message: rudi bruchez: "Re: A tricky update close to be dangerous"
- In reply to: Guy Tanguay: "Cursor in a trigger"
- Next in thread: Andrew John: "Re: Cursor in a trigger"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 25 Feb 2004 13:56:18 -0000
Nope, it's really bad thing. All the locks that your transaction has taken
out are held for the durtion of the trigger, and cursors are slow, so the
locks will be held for a relatively long time, increasing the chance of
blocking problems, which can impact the performance of your database
severely.
-- Jacco Schalkwijk SQL Server MVP "Guy Tanguay" <guy_tanguay@hotmail.com> wrote in message news:3b53412a.0402250552.3ab1babb@posting.google.com... > General Rule? > > Is it a good thing to put a Cursor in a trigger?
- Next message: Dan Guzman: "Re: Procedure parameters from select"
- Previous message: rudi bruchez: "Re: A tricky update close to be dangerous"
- In reply to: Guy Tanguay: "Cursor in a trigger"
- Next in thread: Andrew John: "Re: Cursor in a trigger"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading