Urgent Help

Question

Post reply

Urgent Help

er sql

SSC Eights!

Points: 943
More actions
April 5, 2005 at 12:02 pm

#102467

Hi, I need to know what have done all users logged in my databases, is there a log file that records every transaction executed by the user?.

Thanks a lot

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

AJ Ahrens SSC-Insane Points: 20676 More actions · Answer 1

Unless you have defined one then there is no audit trail of who/what/where/how/why..

Good Hunting!

AJ Ahrens

webmaster@kritter.net

David le Quesne SSCertifiable Points: 5229 More actions · Answer 2

You could use SQL Profiler to record all the SQLBatch activity on your database. If you use the TSQL SQLBatch : Completed event and the Stored Proc RPC : Completed they can record the SQL statements in a log file or a database table. The logged in user and the NT User ID (if available) are also recorded.

David

If it ain't broke, don't fix it...

Daljit-208782 SSChasing Mays Points: 623 More actions · Answer 3

You can choose from the following:

either SQL Profiler Trace or you can use some third party tools lke logexplorer or LogPI etc. Or you can change you C2 Audit level at your server.

Thanks

DonaldW SSCarpal Tunnel Points: 4525 More actions · Answer 4

If the transactions have already been done you are pretty much out of luck unless you already set something up, as AJ indicated. If you are trying to find out what people are currently doing then the other suggestions should give you what you want.

Good luck!

Don

Rudyx - the Doctor SSC-Forever Points: 43695 More actions · Answer 5

I would first ask "why" ? ... (e.g. "Are there unauthorized access to the database ?") ... just curious as to what is driving this question since there are lots of methods and tools that can be used to determine information. It's more of a question of how much time and money you need to invest. Hence the initial question ...

RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

Doug Blystone Ten Centuries Points: 1144 More actions · Answer 6

I agree with Rudy. The 'why' is very important?

I've created some stpred procedures that automatically generate history tables, (based on the schemas of the original table) and also automatically built triggers based on that. It is a very good audit path, but obviously has a lot of overhead. They log previous values and new values so that a complete audit trail can be generated.

LogExplorer is a pretty good tool to see what has been done on your DB as well.