I have received the error message listed below several times within the last
48 hours.
This server has only one database with SQL Server 2000 Enterprise Edition
and Windows 2003 server.
What server performance monitor counter statistics should I be looking at to
determine the cause of this problem?
What can I do to resolve this error?
Thanks,
Error Message
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..Hi,
it looks like you have reached the maximum locks on the server.
Number of locks is determined on availble memory to SQL Server.
Raising the memory available to SQL Server could help.
Danijel
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:4A0366C4-A3D7-4A28-B24B-6B88322D6E3C@.microsoft.com...
> I have received the error message listed below several times within the
> last
> 48 hours.
> This server has only one database with SQL Server 2000 Enterprise Edition
> and Windows 2003 server.
> What server performance monitor counter statistics should I be looking at
> to
> determine the cause of this problem?
> What can I do to resolve this error?
> Thanks,
>
> Error Message
> 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..|||In addition to Danijel's post you will need to monitor the lockblocks counte
r
in the SQLServer:Memory Manager object will tell you when the maximum amoun
t
of locks was reached to produce this error. more memory will obviously help
as the sp_lock configuration when set to 0 will allocate upto 40% of SQL
memory to locks before this happens. so obviously increasing the amount of
memory(assuming that U are running 2K3 OS Advanced then you a can add upto
8Gb of memory)
"Danijel Novak" wrote:
> Hi,
> it looks like you have reached the maximum locks on the server.
> Number of locks is determined on availble memory to SQL Server.
> Raising the memory available to SQL Server could help.
> Danijel
>
> "Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
> news:4A0366C4-A3D7-4A28-B24B-6B88322D6E3C@.microsoft.com...
>
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment