Auditing all tables in a database

I have an application that we purchased that accesses it's database in SQL
Server 2000. I wanted to know what tables the application accesses when a
certain function is performed.
I thought that I could add a trigger to each table that would insert a flag
into a new table but there are almost 700 tables in the database and this
would take forever to do.
Is there something else I can do to identify what tables are
updated/inserted when I perform a function in an application?
Any help is much appreciated.Paul wrote:
> I have an application that we purchased that accesses it's database in SQL
> Server 2000. I wanted to know what tables the application accesses when a
> certain function is performed.
> I thought that I could add a trigger to each table that would insert a fla
g
> into a new table but there are almost 700 tables in the database and this
> would take forever to do.
> Is there something else I can do to identify what tables are
> updated/inserted when I perform a function in an application?
> Any help is much appreciated.
>
Profiler...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:790A61DB-DA9E-4B12-B1B2-392D4338A27B@.microsoft.com...
>I have an application that we purchased that accesses it's database in SQL
> Server 2000. I wanted to know what tables the application accesses when a
> certain function is performed.
> I thought that I could add a trigger to each table that would insert a
> flag
> into a new table but there are almost 700 tables in the database and this
> would take forever to do.
> Is there something else I can do to identify what tables are
> updated/inserted when I perform a function in an application?
> Any help is much appreciated.
>
SQL Profiler will show you this.
David|||I thought of this also but profiler keeps giving me all tranasctions for all
databases. I tried filtering the output to include just the one database bu
t
it still gives me all transactions.
I will try and revisit this and see if I can somehow filter everything else
out.
Thanks for the help.
"David Browne" wrote:

> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:790A61DB-DA9E-4B12-B1B2-392D4338A27B@.microsoft.com...
> SQL Profiler will show you this.
> David
>
>|||Use Profiler
Arnie Rowland
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:790A61DB-DA9E-4B12-B1B2-392D4338A27B@.microsoft.com...
>I have an application that we purchased that accesses it's database in SQL
> Server 2000. I wanted to know what tables the application accesses when a
> certain function is performed.
> I thought that I could add a trigger to each table that would insert a
> flag
> into a new table but there are almost 700 tables in the database and this
> would take forever to do.
> Is there something else I can do to identify what tables are
> updated/inserted when I perform a function in an application?
> Any help is much appreciated.
>|||You have to set the filter before you start a Trace. You can filter by
database -even by the Objectname (Function name).
Arnie Rowland
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:82A95124-4F42-499E-8867-EF16F272C058@.microsoft.com...[vbcol=seagreen]
>I thought of this also but profiler keeps giving me all tranasctions for
>all
> databases. I tried filtering the output to include just the one database
> but
> it still gives me all transactions.
> I will try and revisit this and see if I can somehow filter everything
> else
> out.
> Thanks for the help.
>
> "David Browne" wrote:
>|||The filter should work. Use DatabaseID. Get the id from sysdatabases.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Paul" wrote:
[vbcol=seagreen]
> I thought of this also but profiler keeps giving me all tranasctions for a
ll
> databases. I tried filtering the output to include just the one database
but
> it still gives me all transactions.
> I will try and revisit this and see if I can somehow filter everything els
e
> out.
> Thanks for the help.
>
> "David Browne" wrote:
>