Re: Profiler Interaction with SQL Server-Documentation
- From: "DrinkN1" <DrinkN1@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 6 Sep 2005 17:20:40 -0700
Actually, the problem is with a Blocking Process. When the trace is on, the
process functions normally. When the trace is off, then we experience
extremely sporadic blocks where one process is holding up an entire string of
others that are attempting to access the same table.
"David Gugick" wrote:
>
> SQL Trace should not cause any problems with SQL Server operation.
> Profiler just uses SQL Trace (in a rather inefficient, underperforming
> way) to view database activity. Depending on the level of detail you are
> collecting and the query load on the server, you may be causing a
> performance hit on SQL Server which is slowing down transaction enough
> that you might not be seeing some problems like Deadlocks any longer.
>
> What issues are you having?
>
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
>
.
- References:
- Profiler Interaction with SQL Server-Documentation
- From: DrinkN1
- Re: Profiler Interaction with SQL Server-Documentation
- From: David Gugick
- Profiler Interaction with SQL Server-Documentation
- Prev by Date: SQL profiler question
- Next by Date: Re: SQL profiler question
- Previous by thread: Re: Profiler Interaction with SQL Server-Documentation
- Next by thread: DIFFERENTIAL Backup Problem
- Index(es):
Relevant Pages
|