Sql 2000 Profiler question

14 Jun 2006 2:52 PM

Joe D

From time to time I get the following error:

"Some trace events have not been reported to SQL Profiler because the server
has reached its maximum amount of available memory for the process."

The last time I ran into this (last night) I was running SQL Profiler from
my desktop, against a production database and storing the output in a
separate database on the same production server.

My question is, which server's memory is this message talking about? (i.e.
my desktop or the production server?).

TIA,
Joe

14 Jun 2006 5:05 PM

Sue Hoegemeier

On the SQL Server side but it's the process and the memory
for the process. In and of itself, it doesn't mean you have
memory problems on the server. Usually it just means that
you are trying to capture too many events on a busy server.
Are you tracing the results directly to a table on that
server? That will negatively impact performance. Trace to a
file and then you can import the trace file for analysis.
You may also want to make sure you are only collecting the
information you really need and try reducing the number of
events.
Try using server side traces instead. It uses fewer
resources and you won't miss events you are trying to
capture.

-Sue

On Wed, 14 Jun 2006 09:52:57 -0500, "Joe D"
<jkdrisc***@qg.com> wrote:

Show quote

>From time to time I get the following error:
>
>"Some trace events have not been reported to SQL Profiler because the server
>has reached its maximum amount of available memory for the process."
>
>The last time I ran into this (last night) I was running SQL Profiler from
>my desktop, against a production database and storing the output in a
>separate database on the same production server.
>
>My question is, which server's memory is this message talking about? (i.e.
>my desktop or the production server?).
>
>TIA,
>Joe
>