October 27, 2005 at 12:53 pm
this is the error in the sql server log for the reason my job failed. I have changed the times of the job, to be at a time when there would be no/few users and yet I still get this more often than not. Any ideas as to why or how to fix it???? Thanks in advance!!!!
ERROR:
The SQL Server cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users or ask the system administrator to check the SQL Server lock and memory configuration..
October 28, 2005 at 12:17 pm
I'm no expert in SQL2K5 (yet) but check out the results of:
sp_configure 'locks'
maybe it needs to be 'tweaked' ...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
October 28, 2005 at 12:57 pm
October 28, 2005 at 1:15 pm
It's not that bad ... locks and couple of memory thiongs in sp)_configure are still the only ones that require reboots. The reason locks reared it's ugly head is because you're probobly using the server more and data volume is growing, requiring more locks. If you are using the 'default', there may be a bit of a 'bug' at work because the default settings give a minimum of 5000 and a maximum 2147483648 locks. SQL Server is supposed to 'auto-adjust' this setting. The only reason that I can think of is beacuse you may be running low on memory for the SQL Server (this too is supposed to be another 'dynamic' thing.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
October 28, 2005 at 1:19 pm
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply