|
|
Posted by LaMoRt on 11/27/07 03:07
On Nov 23, 6:32 am, Erland Sommarskog <esq...@sommarskog.se> wrote:
> LaMoRt (cwe...@gmail.com) writes:
> > Yes, it is a data that has been updated and i want to track back the
> > person
> > who did the transaction. Any way to find it in this kind of situation.
> > I'm using SQL2000 actually. So anything that can help me for this?
>
> If the database is in full recovery, you could use a log reader. There
> are a couple on the market, and I've lost track of them all. Lumigent
> was the first in this field, and for a long time the only player on
> the market. Log PI has also been around for a while now. I see that
> Red Gate has SQL Log Rescue which currently is free.
>
> If the database is in simple recovery, or you have truncated the log
> without backing it up since this update appeared, you can forget about it.
>
> And I should add that even with a log reader, it can be quite a tedious
> task to find the culprit.
>
> --
> Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
>
> Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Thanks will try it out..
Navigation:
[Reply to this message]
|