Re: Triggers reverting

From: Wayne Snyder (wsnyder_at_computeredservices.com)
Date: 03/16/04 

Date: Tue, 16 Mar 2004 10:30:03 -0500

If the database you mention contains the Triggers which reverted, then
probably the recovery restored the original version of the triggers...

If that is so, it suggests that you did not do up-to the minute recovery
without loss of data by restoring all of the transaction logs...This means
that you might also be missing some data... 

-- 
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Greg M" <gam@rawlingscompany.com> wrote in message
news:807C699F-8C0E-475D-82E6-F0B5B236329A@microsoft.com...
> This past week, a production change was made in our SQL Server database.
This change included updating 3 triggers on 3 different tables.  The changes
were applied and all changes were tested and verified.  The nature of the
triggers was altered to send an email in the case of a mass update
occurring.  Today, I noticed that a mass update had occurred on one of the
tables but no email was sent.  I examined the trigger to see why it was not
working and discovered that one of the old triggers with no email was still
in place.  This trigger was verified to be in place on the day the change
went into production and tested so I am 100% certain that it was there and
working.  It appears that SQL Server reverted back to the previous version
in this case.  We have experienced this several times in the past with views
and stored procedures as well, but have always attributed it to an improper
production change.  We are using SQL Server 2000 with service pack 3.  Also,
searching the SQL Server logs, I found that Master4IDR was systematically
restored at 11:00 pm on the night of the change.  I am not certain exactly
what that is doing or why or if this is part of the issue.  I am trying to
develop an satisfactory explanation for this occurrence and to hopefully
prevent this from occurring again.  Any help is greatly appreciated.

Relevant Pages

  • Re: Audit trail for web application
    ... This is more of a SQL Server question than an ASP.NET question. ... with implenting auditing at the application level or using table triggers is ... There are also 3rd party database auditing tools that should do ... > I am trying one approach with the help of triggers. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: SQL Server Express versus Access (In the World Series of Love)
    ... If your need involve a form, then triggers are not an appropriate tool: ... after a change in the database. ... OF triggers to achieve the same, say, over view, so, advantage to Jet. ... MS SQL Server may have a horse shoe maker right out of the box, ...
    (microsoft.public.access.modulesdaovba)
  • Re: New to SQL server
    ... it is called triggers. ... ANYTHING THAT YOU CAN DO IN JET IS BABY TALK COMPARED TO WHAT WE CAN DO ... anything that you can do in JET that I can't do in SQL Server ... self-referencing FKs and inline constraints. ...
    (microsoft.public.access.adp.sqlserver)
  • Write conflict error after adding trigger to table
    ... I have inherited an Access adp that directly connects to SQL Server. ... that database. ... stored proc in the database window instead of through the form, ... is preventing me from rolling these triggers to production where other apps ...
    (microsoft.public.access.adp.sqlserver)
  • Re: need information for "Before Select" Trigger
    ... As i've added "Enforced Constraints" ... There are no BEFORE SELECT triggers. ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ... Books Online for SQL Server 2005 at ...
    (comp.databases.ms-sqlserver)