December 1, 2008 at 10:41 am
Hi,
Long time since I've been reading much here!
What I need to do is to audit not changes but access.
Ideally would like to do it for just one table (that has more sensitive data), of course I could log all logins and attempts. I figured my way would be better for
- performance, less writes
- easier for me to keep an eye on, as we will only be recording a small proportion of transactions.
Anyway look forward to any views/ideas, thanks
P
December 1, 2008 at 11:10 am
Profiler/SQL Trace is really your only choice here. Set up a trace to capture stuff hitting the table.
December 1, 2008 at 11:24 am
Thanks Steve,
Do you think I would be better with standard auditing?
P
December 1, 2008 at 11:28 am
What is standard auditing?
In 2000, there isn't any good way to do this. Triggers won't help. Instead you'd have to set up a trace that would capture SELECTs against this table. The filtering in 2000's trace can be flaky, so you might need to capture everything, then delete out that data not referencing your table.
I'd log this to a table in a separate database, trim it on occassion, and use that for your auditing.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply