June 27, 2011 at 9:43 am
Thanks, I accept what you said. Just I have one quick question is any one using the log reader and whether the Log file (.LDF) stores the user name/ Date time/Query/ Machine name from where the changes were done.
In future within our team itself if someone did the changes we have to prove that one. Just I am finding the solution for that one too.
Thanks,
JK
June 27, 2011 at 10:38 am
jvskarthick (6/27/2011)
Thanks, I accept what you said. Just I have one quick question is any one using the log reader and whether the Log file (.LDF) stores the user name/ Date time/Query/ Machine name from where the changes were done.In future within our team itself if someone did the changes we have to prove that one. Just I am finding the solution for that one too.
Thanks,
JK
you'll get user/date time and query but not the hostname.
---------------------------------------------------------------------
June 28, 2011 at 12:41 pm
If this is SQL 2008, can't you use auditing? I haven't tried it (yet, but we will next year), but according to the docs, you can set up a file directory that can only be written to by the SQL Service account, and direct the audit to write to that file, and then you can set up audits to your hearts' content, depending upon how much disk space you want to burn. While a DBA could turn that off, I believe you can audit who did that (last thing it writes). And the file is binary, and can be blocked by NTFS (as long as the DBA doesn't have the service account password). Could this work in this case?
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply