August 16, 2007 at 7:44 am
Can anyone explain the SQLServer:Memory Manager Lock Memory counter? If a user is importing a table into my sql server, I see this counter go from zero to 90 or so and then it takes time for the counter to SLOWLY return to zero, well after the table has been imported. Is importing/exporting tables the only way to affect this counter? How do I see what is causing this counter to change? Thanks
August 16, 2007 at 8:57 am
Try the SQL Profiler.
August 16, 2007 at 9:05 am
Actually I am unable to run the Profiler while my production floor is up and running. After about 5 minutes, the sql server starts to bog down and affect the floor. I run a query on the sysProcesses table to see who's logged in and what their spid is doing but yesterday when the lock memory increased, no one was importing/exporting a table. If i did run the Profiler what would I be looking for exactly? Also, can someone explain to me what the lock memory is? Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply