audit log

Excuse the naive question, but I have heard about SQL Server's "transaction
log" and I am wondering if this can be viewed to see all of the transactions
that occurred in past X amount of time. Is this feasible?
Are than any other solutions for audit trail besides putting triggers on
every table to log everything?
Thanks.
You can "view" the transaction log using third-party programs like LogPI and
Log Explorer (Google for them) but it's not a very pleasant experience --
there's a surprisingly large amount of data to sort through. Triggers are
definitely a good bet for a manageable audit trail in the database. You can
also look at SQL Server's built-in auditing facilities. Check out the
topic, "Auditing SQL Server Activity" in BOL.
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
"Mike W" <mikeotown@.nospam.msn.com> wrote in message
news:eMcABUdFFHA.4004@.tk2msftngp13.phx.gbl...
> Excuse the naive question, but I have heard about SQL Server's
"transaction
> log" and I am wondering if this can be viewed to see all of the
transactions
> that occurred in past X amount of time. Is this feasible?
> Are than any other solutions for audit trail besides putting triggers on
> every table to log everything?
> Thanks.
>
|||Here are some links: http://vyaskn.tripod.com/administration_faq.htm#q1
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Mike W" <mikeotown@.nospam.msn.com> wrote in message
news:eMcABUdFFHA.4004@.tk2msftngp13.phx.gbl...
Excuse the naive question, but I have heard about SQL Server's "transaction
log" and I am wondering if this can be viewed to see all of the transactions
that occurred in past X amount of time. Is this feasible?
Are than any other solutions for audit trail besides putting triggers on
every table to log everything?
Thanks.
|||If you talking detailed auditing such as might be required by the dreaded
Sarbnes/Oxely Act, then there are also some third party (read - not cheap)
tools for such things. Lumigent is one company I know of.
Bob Castleman
DBA Poseur
"Mike W" <mikeotown@.nospam.msn.com> wrote in message
news:eMcABUdFFHA.4004@.tk2msftngp13.phx.gbl...
> Excuse the naive question, but I have heard about SQL Server's
> "transaction log" and I am wondering if this can be viewed to see all of
> the transactions that occurred in past X amount of time. Is this
> feasible?
> Are than any other solutions for audit trail besides putting triggers on
> every table to log everything?
> Thanks.
>

audit log

Excuse the naive question, but I have heard about SQL Server's "transaction
log" and I am wondering if this can be viewed to see all of the transactions
that occurred in past X amount of time. Is this feasible?
Are than any other solutions for audit trail besides putting triggers on
every table to log everything?
Thanks.You can "view" the transaction log using third-party programs like LogPI and
Log Explorer (Google for them) but it's not a very pleasant experience --
there's a surprisingly large amount of data to sort through. Triggers are
definitely a good bet for a manageable audit trail in the database. You can
also look at SQL Server's built-in auditing facilities. Check out the
topic, "Auditing SQL Server Activity" in BOL.
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"Mike W" <mikeotown@.nospam.msn.com> wrote in message
news:eMcABUdFFHA.4004@.tk2msftngp13.phx.gbl...
> Excuse the naive question, but I have heard about SQL Server's
"transaction
> log" and I am wondering if this can be viewed to see all of the
transactions
> that occurred in past X amount of time. Is this feasible?
> Are than any other solutions for audit trail besides putting triggers on
> every table to log everything?
> Thanks.
>|||Here are some links: http://vyaskn.tripod.com/administration_faq.htm#q1
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Mike W" <mikeotown@.nospam.msn.com> wrote in message
news:eMcABUdFFHA.4004@.tk2msftngp13.phx.gbl...
Excuse the naive question, but I have heard about SQL Server's "transaction
log" and I am wondering if this can be viewed to see all of the transactions
that occurred in past X amount of time. Is this feasible?
Are than any other solutions for audit trail besides putting triggers on
every table to log everything?
Thanks.|||If you talking detailed auditing such as might be required by the dreaded
Sarbnes/Oxely Act, then there are also some third party (read - not cheap)
tools for such things. Lumigent is one company I know of.
Bob Castleman
DBA Poseur
"Mike W" <mikeotown@.nospam.msn.com> wrote in message
news:eMcABUdFFHA.4004@.tk2msftngp13.phx.gbl...
> Excuse the naive question, but I have heard about SQL Server's
> "transaction log" and I am wondering if this can be viewed to see all of
> the transactions that occurred in past X amount of time. Is this
> feasible?
> Are than any other solutions for audit trail besides putting triggers on
> every table to log everything?
> Thanks.
>

Attaching & Detaching SQL 2000 Databases

Why is it that sometimes you can detach a database, delete the transaction
log, reattched the database and a new transaction log will be created; and
other times, the attach fails with an error message indicating that the
transaction log file name (including the path) "may be incorrect"?
Thanks,
Ross
Why detach and delete the transaction log? I've seen the
error before when others have done the same - it's not
really the best thing to do.
Some reasons for it not attaching are it not being cleanly
detached, issues or corruption in the database before
detaching, not using the with recovery clause, not using
sp_attach_single_file_db, using sp_attach_single_file_db
when the database had multiple log files.
-Sue
On Mon, 23 Jan 2006 10:37:29 -0600, "Ross Culver"
<rculver@.ranger-systems.com> wrote:

>Why is it that sometimes you can detach a database, delete the transaction
>log, reattched the database and a new transaction log will be created; and
>other times, the attach fails with an error message indicating that the
>transaction log file name (including the path) "may be incorrect"?
>Thanks,
>Ross
>

Attaching & Detaching SQL 2000 Databases

Why is it that sometimes you can detach a database, delete the transaction
log, reattched the database and a new transaction log will be created; and
other times, the attach fails with an error message indicating that the
transaction log file name (including the path) "may be incorrect"?
Thanks,
RossWhy detach and delete the transaction log? I've seen the
error before when others have done the same - it's not
really the best thing to do.
Some reasons for it not attaching are it not being cleanly
detached, issues or corruption in the database before
detaching, not using the with recovery clause, not using
sp_attach_single_file_db, using sp_attach_single_file_db
when the database had multiple log files.
-Sue
On Mon, 23 Jan 2006 10:37:29 -0600, "Ross Culver"
<rculver@.ranger-systems.com> wrote:

>Why is it that sometimes you can detach a database, delete the transaction
>log, reattched the database and a new transaction log will be created; and
>other times, the attach fails with an error message indicating that the
>transaction log file name (including the path) "may be incorrect"?
>Thanks,
>Ross
>