Identifying what Apps are using a database

I'm looking for a little insight on identifying what apps
are updating a particular database. Basically we have a
front end developed for the db but some people may have
created Access dbs and processes in Access to do updates.
I need to determine if this is happening since we may be
moving the db to a different sql server. SQL Profiler
would work, but it's hit and miss. Plus I'd have to let
it run for a few days which would create a huge trace
file. If I did let it run for a few days, I still may not
capture and activity from Access if they didn't happen to
run any Access updates during that time. Is there
anything out there that can help me?
Thanks,
Van Jones"Van Jones" <anonymous@.discussions.microsoft.com> wrote in message
news:012401c4f75f$6fe0e520$a601280a@.phx.gbl...
> I'm looking for a little insight on identifying what apps
> are updating a particular database. Basically we have a
> front end developed for the db but some people may have
> created Access dbs and processes in Access to do updates.
> I need to determine if this is happening since we may be
> moving the db to a different sql server. SQL Profiler
> would work, but it's hit and miss. Plus I'd have to let
> it run for a few days which would create a huge trace
> file. If I did let it run for a few days, I still may not
> capture and activity from Access if they didn't happen to
> run any Access updates during that time. Is there
> anything out there that can help me?
> Thanks,
> Van Jones
I would still go with Profiler. Take a look at the Filters tab. You can
do things like: NOT LIKE and add all of the known applications that will
log in. You can weed out just about all the activity that you don't want
to see. Then your trace file will not be enormous.
The other suggestion is to turn on profiler and ask everyone to hit the
server with their updates so that you can capture everything in one go.
Rick Sawtell
MCT, MCSD, MCDBA|||
>--Original Message--
>"Van Jones" <anonymous@.discussions.microsoft.com> wrote
in message
>news:012401c4f75f$6fe0e520$a601280a@.phx.gbl...
apps[vbcol=seagreen]
updates.[vbcol=seagreen]
not[vbcol=seagreen]
to[vbcol=seagreen]
>
>I would still go with Profiler. Take a look at the
Filters tab. You can
>do things like: NOT LIKE and add all of the known
applications that will
>log in. You can weed out just about all the activity
that you don't want
>to see. Then your trace file will not be enormous.
>The other suggestion is to turn on profiler and ask
everyone to hit the
>server with their updates so that you can capture
everything in one go.
>
>Rick Sawtell
>MCT, MCSD, MCDBA
>
>.
Yea, I figure profiler might be the only way. The problem
is...is that I don't know if anybody has any Access
processes that update the db. I've been told that they
might. If they do, it could be quartly or even year end
processes that I wouldn't capture if I ran a trace for a
few days.|||"Van Jones" <anonymous@.discussions.microsoft.com> wrote in message
news:1d5c01c4f761$bc059f70$a401280a@.phx.gbl...
>
> in message
> apps
> updates.
> not
> to
> Filters tab. You can
> applications that will
> that you don't want
> everyone to hit the
> everything in one go.
> Yea, I figure profiler might be the only way. The problem
> is...is that I don't know if anybody has any Access
> processes that update the db. I've been told that they
> might. If they do, it could be quartly or even year end
> processes that I wouldn't capture if I ran a trace for a
> few days.
Can you take an inventory of the applications that are hitting your
database? You should have this list regardless.
Another method. (Muahahahaha) Change the login credentials.
Rick Sawtell
MCT, MCSD, MCDBA