Home All Groups Group Topic Archive Search About
Author
2 Nov 2006 7:30 PM
Jamal
All,

Is there any way to track what tables are being changed by an application.
We have a third-party application that uses SQL server and for support
purpose, I would like to know what tables are being updated by certain
processes. Are there any free tools out there that can do that. Any help
would be appreciated.

Jamal

Author
2 Nov 2006 7:40 PM
Arnie Rowland
With SQL Server 2005, it could be as 'simple' as using a DDL Trigger.

With SQL Server 2000, you could use a Profiler trace. There are a number of
third party products designed to track such actions. (I don't think that
there are any 'free' third party tools.)

Audit Tools
   ApexSQL Audit http://www.apexsql.com/sql_tools_audit.asp
   Lumigent Adit DB http://www.lumigent.com/products/auditdb.html
   OmniAudit http://www.krell-software.com/omniaudit/index.asp
   SQLLog
http://www.rlpsoftware.com/mainframe.asp?contents=SQLLog.asp&mainmenu=SQLLog&submenu=Info
   Upscene SQL Log Manager
http://www.upscene.com/index.htm?./products/audit/mssqllm_main.htm
   DB Audit Expert http://www.softtreetech.com/dbaudit/


--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous

You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf


Show quote
"Jamal" <jma@newsgroups.nospam> wrote in message
news:OUeUbVr$GHA.4428@TK2MSFTNGP04.phx.gbl...
> All,
>
> Is there any way to track what tables are being changed by an application.
> We have a third-party application that uses SQL server and for support
> purpose, I would like to know what tables are being updated by certain
> processes. Are there any free tools out there that can do that. Any help
> would be appreciated.
>
> Jamal
>
>
Author
2 Nov 2006 8:42 PM
Jamal
Thanks Arnie for the reply.

With the DDL trigger you have to create one for each table.

Any third party tool that you recommend.


Jamal
Show quote
"Arnie Rowland" <ar***@1568.com> wrote in message
news:%23EgpDbr$GHA.4472@TK2MSFTNGP03.phx.gbl...
> With SQL Server 2005, it could be as 'simple' as using a DDL Trigger.
>
> With SQL Server 2000, you could use a Profiler trace. There are a number
> of third party products designed to track such actions. (I don't think
> that there are any 'free' third party tools.)
>
> Audit Tools
>   ApexSQL Audit http://www.apexsql.com/sql_tools_audit.asp
>   Lumigent Adit DB http://www.lumigent.com/products/auditdb.html
>   OmniAudit http://www.krell-software.com/omniaudit/index.asp
>   SQLLog
> http://www.rlpsoftware.com/mainframe.asp?contents=SQLLog.asp&mainmenu=SQLLog&submenu=Info
>   Upscene SQL Log Manager
> http://www.upscene.com/index.htm?./products/audit/mssqllm_main.htm
>   DB Audit Expert http://www.softtreetech.com/dbaudit/
>
>
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
>
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
>
> "Jamal" <jma@newsgroups.nospam> wrote in message
> news:OUeUbVr$GHA.4428@TK2MSFTNGP04.phx.gbl...
>> All,
>>
>> Is there any way to track what tables are being changed by an
>> application. We have a third-party application that uses SQL server and
>> for support purpose, I would like to know what tables are being updated
>> by certain processes. Are there any free tools out there that can do
>> that. Any help would be appreciated.
>>
>> Jamal
>>
>>
>
>
Author
2 Nov 2006 8:57 PM
Aaron Bertrand [SQL Server MVP]
> With the DDL trigger you have to create one for each table.

DDL triggers?  No you don't.  If you're talking about changing data, yes
that is true.  But DDL triggers captures changes to table structure / schema
/ database objects, not data.

A
Author
2 Nov 2006 9:30 PM
Jamal
I was talking about changing data.

Show quote
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message
news:%23SyGQFs$GHA.3536@TK2MSFTNGP03.phx.gbl...
>> With the DDL trigger you have to create one for each table.
>
> DDL triggers?  No you don't.  If you're talking about changing data, yes
> that is true.  But DDL triggers captures changes to table structure /
> schema / database objects, not data.
>
> A
>
Author
2 Nov 2006 9:47 PM
Arnie Rowland
In your original post, you indicated that you wanted to "track what tables
are being changed".

I guess I misunderstood you and assumed that you want to know "what tables
had been changed" -when in fact you wanted to know about the data that had
been changed in the tables. Correct?

If that is correct, my previous response is unnecessary.

There are several methods of tracking data changes, including Triggers on
EACH table.

The Third party tools provide a good option.

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous

You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf


Show quote
"Jamal" <jma@newsgroups.nospam> wrote in message
news:%23WbPQYs$GHA.4328@TK2MSFTNGP03.phx.gbl...
>I was talking about changing data.
>
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in
> message news:%23SyGQFs$GHA.3536@TK2MSFTNGP03.phx.gbl...
>>> With the DDL trigger you have to create one for each table.
>>
>> DDL triggers?  No you don't.  If you're talking about changing data, yes
>> that is true.  But DDL triggers captures changes to table structure /
>> schema / database objects, not data.
>>
>> A
>>
>
>
Author
2 Nov 2006 10:07 PM
Aaron Bertrand [SQL Server MVP]
For future reference, changing data != DDL.  Changing data = DML.



Show quote
"Jamal" <jma@newsgroups.nospam> wrote in message
news:%23WbPQYs$GHA.4328@TK2MSFTNGP03.phx.gbl...
>I was talking about changing data.
Author
2 Nov 2006 10:21 PM
Erland Sommarskog
Jamal (jma@newsgroups.nospam) writes:
> I was talking about changing data.

There are a couple of third-party tools out there. Some works by installing
triggers, others by reading the transaction log.

An example of trigger-based auditing is SQL Audit from Red Matrix.

Example of log readers are Lumigent Log Explorer and Log PI. Lumgiment
also has a more elaborate tool that use to be called Entegra, but I
believe they have a new name.

I have not tried any of them myself.


--
Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Author
1 Dec 2006 5:50 PM
valdez.delia
To track data changes, im using the www.auditdatabase.com tools.
Are free and generates audit triggers for SQL Server and other popular
DBMS's.

Delia.

Erland Sommarskog ha escrito:

Show quote
> Jamal (jma@newsgroups.nospam) writes:
> > I was talking about changing data.
>
> There are a couple of third-party tools out there. Some works by installing
> triggers, others by reading the transaction log.
>
> An example of trigger-based auditing is SQL Audit from Red Matrix.
>
> Example of log readers are Lumigent Log Explorer and Log PI. Lumgiment
> also has a more elaborate tool that use to be called Entegra, but I
> believe they have a new name.
>
> I have not tried any of them myself.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Author
1 Dec 2006 5:50 PM
valdez.delia
To track data changes, im using the www.auditdatabase.com tools.
Are free and generates audit triggers for SQL Server and other popular
DBMS's.

Delia.

Erland Sommarskog ha escrito:

Show quote
> Jamal (jma@newsgroups.nospam) writes:
> > I was talking about changing data.
>
> There are a couple of third-party tools out there. Some works by installing
> triggers, others by reading the transaction log.
>
> An example of trigger-based auditing is SQL Audit from Red Matrix.
>
> Example of log readers are Lumigent Log Explorer and Log PI. Lumgiment
> also has a more elaborate tool that use to be called Entegra, but I
> believe they have a new name.
>
> I have not tried any of them myself.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

AddThis Social Bookmark Button