Databases
StackOverflow2013
Postsdbo
POPrevent trigger from firing
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPrevent trigger from firing
    primarykey
    data
    text
    <p>I have the following trigger</p> <p>First trigger:</p> <pre><code>ALTER TRIGGER [dbo].[DIENSTLEISTUNG_Update] ON [dbo].[DIENSTLEISTUNG] INSTEAD OF UPDATE AS BEGIN SET NOCOUNT ON; DECLARE @intNewID int INSERT INTO [DIENSTLEISTUNG] (DESCRIPTION, QUANTITY, PRICE, AZ_MO, AZ_DI,AZ_MI,AZ_DO,AZ_FR, AZ_SA,AZ_SO,DIENSTLEISTUNGSART_ID, UPDATE_USER, UPDATE_DATE, PERMISSIONS, KONTRAKTPOSITION,ITEMNUMBER, PRIORITY, VALID) SELECT i.DESCRIPTION, i.QUANTITY, i.PRICE, i.AZ_MO, i.AZ_DI,i.AZ_MI,i.AZ_DO,i.AZ_FR, i.AZ_SA,i.AZ_SO,i.SERVICETYPE_ID, i.UPDATE_USER,GETDATE(), i.PERMISSIONS, i.KONTRAKTPOSITION,i.ITEMNUMBER, i.PRIORITY, 'Y' FROM INSERTED i JOIN deleted d ON i.ID=d.ID WHERE i.PRICE&lt;&gt;d.PRICE or i.DESCRIPTION&lt;&gt;d.DESCRIPTION IF ( UPDATE (PRICE) OR UPDATE (DESCRIPTION) ) UPDATE S SET s.VALID = 'N' FROM SERVICE s JOIN INSERTED i ON I.ID = S.ID IF UPDATE(PRIORITY) UPDATE s SET s.PRIORITY= i.PRIORITY FROM SERVICE s JOIN INSERTED i ON i.ID = s.ID SET NOCOUNT OFF; END </code></pre> <p>The first Trigger copies an entire row with a new ID if a change in the original row happens, also the trigger set a flag. The old row gets the flag <code>VALID = 'N'</code> and the new row gets the flag <code>VALID = 'Y'</code>. The trigger only creates a new row if <code>PRICE</code> or <code>DESCRIPTION</code> are updated. So far so good. </p> <p>My problem is that if I want to update the <code>PRIORITY</code> in the new row the trigger fires again and sets the flag to <code>VALID = 'N'</code>. That should not happen. I want only to update the priority without creating a new row or update a another column.</p> <p>Thanks for help</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPaks
    1. USPaks
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPrevent trigger from firing
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPrevent trigger from firing
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPrevent trigger from firing
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAn excellent example of triggers getting complex quickly. I'd remove all your triggers, and move the data access to stored procedures that incorporate the trigger functionality.
      singulars
      1. POPrevent trigger from firing
      1. USAndomar
    2. COiam new in sql and i have no experience with stored procedures. Maybe you can help me with that?
      singulars
      1. POPrevent trigger from firing
      1. USPaks
    3. COStored procedures are easier than triggers. You can find many good [tutorials on Google](https://www.google.com/search?q=+introduction+to+sqlserver+stored+procedure)
      singulars
      1. POPrevent trigger from firing
      1. USAndomar
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload