July 11, 2008 at 7:53 am
Hi all,
I am new to this forum. For a project task, we need to trace any kind of user activity with the database, like, which user is accessing what piece of data, at what date/time from which system (IP Addr) and what he/she doing with that data (like INSERT/SELECT/UPDATE/DELETE). This is same as database auditing.
My problem is, where to implement it, Client side or Server side? If client side then, we need to push all these data to server and if at Server side, we need to pull data. Which is economical, in terms of Traffic, speed, processing time etc? As server will be in some Intranet site, we need to assume thousands of users. So Server will be busy with normal Request/Grant work, plus need to keep this required Auditing history info also for each activity/transaction.
Please help me in this regards. I am using SQL 2000 presently and shortly migrating to 2005 for this task.
___
Regards,
Rajeev M Vandakar, B.lore.
July 11, 2008 at 8:43 am
The best way to do this is run a trace on the server. You can set that up with either the Profiler (you can get to that from Tools in Management Studio), or by using system procs. Search for "trace" in Books Online and it will give you articles on exactly how to set this up.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply