Re: Tracking changes to a DB
From: Andrew J. Kelly (sqlmvpnoooospam_at_shadhawk.com)
Date: 05/15/04
- Next message: Joe Richards [MVP]: "Re: Test questions? (off topic)"
- Previous message: Andrew J. Kelly: "Re: Memory"
- In reply to: jme (a t) cimex (d0t) com (d0t) mx: "Tracking changes to a DB"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 15 May 2004 10:39:59 -0400
The easiest way in the short term to investigate a situation such as this is
to run a profiler trace. You can then see exactly what commands are being
issued against the table and what the values being used are.
-- Andrew J. Kelly SQL MVP "jme (a t) cimex (d0t) com (d0t) mx" <"jme (a t) cimex (d0t) com (d0t) mx"> wrote in message news:uzq6P2fOEHA.2920@tk2msftngp13.phx.gbl... > Hi, > > I have a DB managed by SQL-Server 7 SP4. Today, several fields within > one table appeared populated by nulls, when only yesterday they had real > data in them. The rest of the fields of the problematic rows where ok > (but they where mostly foreign keys and of little real value). > > After searching a bit through these groups, I learned that SQL Server > does have a logging facility, but it is of no practical value, mostly > because you have to buy a third party application to even get to see the > log. Luckily our daily backups took care of the problem and I was able > to restore the data to its original state. > > Still, I am worried of a buggy application setting these values to > nulls. Is there anyway to track (without buying the third party app) > when, where, or how did these fields got nulled? Is there any practical > use in keeping a log file, without buying the third party app? > > TIA > > Javier
- Next message: Joe Richards [MVP]: "Re: Test questions? (off topic)"
- Previous message: Andrew J. Kelly: "Re: Memory"
- In reply to: jme (a t) cimex (d0t) com (d0t) mx: "Tracking changes to a DB"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|