August 15, 2003 at 6:51 am
For the second time in 3 days, my production SQL Server (2000 on NT 4) has gone done due to memory problems.
My hosting facility fixed it the first time by changing the page file size and rebooting. Seemed to work, until last night!
How would I check for a memory leak? Also our error messages don't inidcate what query caused the problem. Should I set up a trace to capture events during the time it seems to happen? (2:20 to 2:30 am)
Could backup jobs be contributing to this by any chance? I do have a backup job scheduled at 2 am every morning.
August 17, 2003 at 7:08 pm
Hi there
I would do this:
a) check the memory config for your instance (more than one btw??) and knock the max memory value down 40 odd meg from the total memory if used
b) run perf monitor, track all processes and their memory usage, this is great for monitoring the time in which the memory growths are occuring and gives you a way to relating it back to working being performed on the server
Cheers
Ck
Chris Kempster
Author of "SQL Server 2k for the Oracle DBA"
Chris Kempster
www.chriskempster.com
Author of "SQL Server Backup, Recovery & Troubleshooting"
Author of "SQL Server 2k for the Oracle DBA"
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply