A large number of database systems provide something like an Auditing Trail or Log.
Sometimes primitive, sometimes difficult to read, sometimes based on data, sometimes based on command/instructions/scripts.
SQL-server lacked (at least in older standard editions) a feature to access the audit information on both data and scripts.
Mike Vessey asked Why? (At least I think he asked why).
My answer to that : I think that there is at least some Auditing trail reading possibility in the latest (or more recent) Enterprise versions of SQLserver.
Would this be sufficient for my situation. At the moment we are looking to change a database from SQLanywhere to SQLserver. SQLanywhere has an Audit trail possibility where scripts can be generated to 'replay' actions. Is something available in SQLserver ?
There is mention of an audit database engine within SQLserver, but I have no experience with this. Building up enough experience with something like an Audit trail takes time and might lead to disappointment.
My question is, what are the possibilities with SQLserver for auditing? And more specific what is build into the engine.
(Not building your own triggers. Not specifically switching on the profiler.)What can be used to audit trail actions which have resulted into a problem, after the problem has occurred ?
Thanks for your time and attention,