Hi,
While tracing some events, i am constantly getting thie
following error message from SQL Server.

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


Due to this, i am unable to collect information about lots
of events and calls to database objects and their
execution duration. Anyone out there knows how to get rid
of this problem? Is this SQL Server DB specific or Windows
specific? I am running SQL Server 2K on Win2K.

TIA

Report this post to a moderator

Hello Kate,

this message basically means that some of the events were dropped on the
server.
That happens when the amount of the events that the server produces in a
unit of time greatly exceeds the amount of events that profiler manages to
read in that unit of time. You could try to mitigate this by:
1. If you connect to the server remotely, try to use the network with higher
bandwith or avoid remote connection altogether.
2. Select fewer events/columns - select only events and columns that you
need.
3. Try using server generated files.
4. If you connect to the server remotely, is your local machine fast enough?

Please let me know if this helps.

Thanks,
Slavik

--
This posting is provided "AS IS" with no warranties, and confers no rights.




"Kate" <aby123@popmail.com> wrote in message
news:1393501c21eaa$71f6f9c0$3b
ef2ecf@TKMSFTNGXA10...
> Hi,
> While tracing some events, i am constantly getting thie
> following error message from SQL Server.
>
> Profiler Message:
> Some trace events have not been reported to SQL Profiler
> because the server has reached its maximum amount of
> available memory for the process.
>
>
> Due to this, i am unable to collect information about lots
> of events and calls to database objects and their
> execution duration. Anyone out there knows how to get rid
> of this problem? Is this SQL Server DB specific or Windows
> specific? I am running SQL Server 2K on Win2K.
>
> TIA

Report this post to a moderator