Sql Profiler trace cannot trace events b/c max amount of available memory has been reached
Posted on 2004-10-04
I have a SQL 2000 database that seems to be running a large amount of transactions at one time to create a 10GB transaction log. I have pinpointed the time this has occurred and it happens between 1 and 2am every night. We just recently upgraded the application so I assume it could be due to that since this hasn't occurred prior to the upgrade. I attempted to do a trace using sql profiler and set the output file size to 30MB to give me a good view of when and how many transactions occur during a specified time. From 11pm-230am I have 18 - 30MB files. From 1:07am - 2:32am 15 of the 18 were created. I have been looking through the files and many of the messages I receive are "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. Does this mean the processes have maxed out the available memory for SQL Server itself? We have 2GB of memory available on the server just for SQL Server. There aren't any messages in the event viewer and I can't see anything in the error logs. I'm very new to this trace thing so please help me understand where to look next??? Thanks in advance!!