August 20, 2004 at 3:16 pm
I am getting the following entries in traces captured from a SQL 2000 server: 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 information is in TextData column. The only other column with data is the EventClass which is: Profiler Message
Does this indicate a problem with total memory on the system or a confirguration parameter that needs changing or something wrong with profiler trace? Too many events and data columns perhaps?
If it were only one or two entries I would not be so concerned but it is hundreds/thousands over the course of a 9 minute trace. We are capturing a lot of info because we are troubleshooting some performance issues and don't have a good idea of what we are looking for.
Any ideas would be appreciated.
Mark
Mark
August 20, 2004 at 4:29 pm
I believe profiler is lossy, so if performance of the server becomes an issue, it will drop events.
If the server is overloaded, you might get this a lot. I'd reduce the number of events captured or run a serverside trace instead of using the client.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply