For some time, I have been trying to determine why we are getting
timeouts under certain conditions using an A2003 front end, SQL2000
backend. I have recently seen several quirky conditions related to a
too-low setting of maxlocksperfile.

Can that setting perhaps cause a timeout if the process is trying to
acquire too many locks?

TIA

Maxlocksperfile is a Jet setting, not SQL Server setting. It
really depends on how you have the Access piece implemented.
If it's an ADP, there is no jet so no. Other than that, it
depends.
If this is just SQL Server and no jet involved, you'd
probably want to start by checking for locking, blocking
issues. You can use the system stored procedures sp_lock,
sp_who2 and query master..sysprocesses.
You may also want to take a look at the following article:
INF: How to Monitor SQL Server 7.0 Blocking
http://support.microsoft.com/?id=251004

-Sue

On Fri, 04 Nov 2005 09:54:12 -0500, elf
<eric@northstarcc.com> wrote:

>For some time, I have been trying to determine why we are getting
>timeouts under certain conditions using an A2003 front end, SQL2000
>backend. I have recently seen several quirky conditions related to a
>too-low setting of maxlocksperfile.
>
>Can that setting perhaps cause a timeout if the process is trying to
>acquire too many locks?
>
>TIA

Thanks, It is DAO.


Sue Hoegemeier wrote:
> Maxlocksperfile is a Jet setting, not SQL Server setting. It
> really depends on how you have the Access piece implemented.
> If it's an ADP, there is no jet so no. Other than that, it
> depends.
> If this is just SQL Server and no jet involved, you'd
> probably want to start by checking for locking, blocking
> issues. You can use the system stored procedures sp_lock,
> sp_who2 and query master..sysprocesses.
> You may also want to take a look at the following article:
> INF: How to Monitor SQL Server 7.0 Blocking
> http://support.microsoft.com/?id=251004
>
> -Sue
>
> On Fri, 04 Nov 2005 09:54:12 -0500, elf
> <eric@northstarcc.com> wrote:
>
>
>>For some time, I have been trying to determine why we are getting
>>timeouts under certain conditions using an A2003 front end, SQL2000
>>backend. I have recently seen several quirky conditions related to a
>>too-low setting of maxlocksperfile.
>>
>>Can that setting perhaps cause a timeout if the process is trying to
>>acquire too many locks?
>>
>>TIA
>
>

So with it being Jet, don't know - that's an Access specific
thing. You'd probably want to ask that in one of the Access
newsgroups.

-Sue

On Tue, 08 Nov 2005 22:55:42 -0500, elf
<eric@northstarcc.com> wrote:

>Thanks, It is DAO.
>
>
>Sue Hoegemeier wrote:
>> Maxlocksperfile is a Jet setting, not SQL Server setting. It
>> really depends on how you have the Access piece implemented.
>> If it's an ADP, there is no jet so no. Other than that, it
>> depends.
>> If this is just SQL Server and no jet involved, you'd
>> probably want to start by checking for locking, blocking
>> issues. You can use the system stored procedures sp_lock,
>> sp_who2 and query master..sysprocesses.
>> You may also want to take a look at the following article:
>> INF: How to Monitor SQL Server 7.0 Blocking
>> http://support.microsoft.com/?id=251004
>>
>> -Sue
>>
>> On Fri, 04 Nov 2005 09:54:12 -0500, elf
>> <eric@northstarcc.com> wrote:
>>
>>
>>>For some time, I have been trying to determine why we are getting
>>>timeouts under certain conditions using an A2003 front end, SQL2000
>>>backend. I have recently seen several quirky conditions related to a
>>>too-low setting of maxlocksperfile.
>>>
>>>Can that setting perhaps cause a timeout if the process is trying to
>>>acquire too many locks?
>>>
>>>TIA
>>
>>