OT: "Profiler" for Access?

Guys,
Is there a tool that I can see what queries are running against an Access
database? The one is similar to Profiler for SQL.
Thanks.Hi
AFAIK three is no such tool, if you are using ODBC then you may want to try
using ODBC tracing, but this would need to be enabled on each client and
would severely impact performance. Another alternative would be to make the
m
linked tables to a SQL Server database and to actually use profiler.
You may want to ask this in an Access News Group.
John
"ME" wrote:

> Guys,
> Is there a tool that I can see what queries are running against an Access
> database? The one is similar to Profiler for SQL.
> Thanks.
>
>|||thanks anyway.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:0CC54221-14C3-42D9-A296-46C75C5B1C29@.microsoft.com...[vbcol=seagreen]
> Hi
> AFAIK three is no such tool, if you are using ODBC then you may want to
> try
> using ODBC tracing, but this would need to be enabled on each client and
> would severely impact performance. Another alternative would be to make
> them
> linked tables to a SQL Server database and to actually use profiler.
> You may want to ask this in an Access News Group.
> John
> "ME" wrote:
>

OT: "Profiler" for Access?

Guys,
Is there a tool that I can see what queries are running against an Access
database? The one is similar to Profiler for SQL.
Thanks.Hi
AFAIK three is no such tool, if you are using ODBC then you may want to try
using ODBC tracing, but this would need to be enabled on each client and
would severely impact performance. Another alternative would be to make them
linked tables to a SQL Server database and to actually use profiler.
You may want to ask this in an Access News Group.
John
"ME" wrote:
> Guys,
> Is there a tool that I can see what queries are running against an Access
> database? The one is similar to Profiler for SQL.
> Thanks.
>
>|||thanks anyway.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:0CC54221-14C3-42D9-A296-46C75C5B1C29@.microsoft.com...
> Hi
> AFAIK three is no such tool, if you are using ODBC then you may want to
> try
> using ODBC tracing, but this would need to be enabled on each client and
> would severely impact performance. Another alternative would be to make
> them
> linked tables to a SQL Server database and to actually use profiler.
> You may want to ask this in an Access News Group.
> John
> "ME" wrote:
>> Guys,
>> Is there a tool that I can see what queries are running against an Access
>> database? The one is similar to Profiler for SQL.
>> Thanks.
>>

OStress tool

Can anyone tell me what 'Avg. TTFR' and 'Avg. TTLR' in the output of Ostress
refer to?
Regards Tim G-JTim,
Just in case anyone else is interested I think I've found the answer: -
TTFR = Time to First Read
TTLR = Time to Last Read
Good luck
Tim G-J
"Tim G-J" wrote:
> Can anyone tell me what 'Avg. TTFR' and 'Avg. TTLR' in the output of Ostress
> refer to?
> Regards Tim G-J

OStress tool

Can anyone tell me what 'Avg. TTFR' and 'Avg. TTLR' in the output of Ostress
refer to?
Regards Tim G-JTim,
Just in case anyone else is interested I think I've found the answer: -
TTFR = Time to First Read
TTLR = Time to Last Read
Good luck
Tim G-J
"Tim G-J" wrote:

> Can anyone tell me what 'Avg. TTFR' and 'Avg. TTLR' in the output of Ostre
ss
> refer to?
> Regards Tim G-J|||Tim,
Just in case anyone else is interested I think I've found the answer: -
TTFR = Time to First Read
TTLR = Time to Last Read
Good luck
Tim G-J
"Tim G-J" wrote:

> Can anyone tell me what 'Avg. TTFR' and 'Avg. TTLR' in the output of Ostre
ss
> refer to?
> Regards Tim G-J