Re: The SQL Server cannot obtain a LOCK resource at this time.

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
Date: Wed, 6 Jul 2005 06:41:56 -0400

How many distribution/merge agents do you have? If you have above 50 you
might want to stagger them to run on different schedules; if they are merge
agents make sure that you are using the concurrent merge agent option. Make
sure you are using pull replication for larger numbers of subscribers (>20).

You also might want to think about migrating to a remote distributor.

--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
""akej via SQLMonster.com"" <forum@xxxxxxxxxxxxxx> wrote in message
news:50E21DA9EA73F@xxxxxxxxxxxxxxxxx
> i saw this kb before i posted my question, however it not really help me,
>
> this error occured on distributor agent, its happen suddenly.
>
>
>
>
> any suggestion.
>
> --
> Message posted via http://www.sqlmonster.com

.

Follow-Ups:
- Re: The SQL Server cannot obtain a LOCK resource at this time.
  - From: \"akej via SQLMonster . com\"

References:
- The SQL Server cannot obtain a LOCK resource at this time.
  - From: \"akej via SQLMonster . com\"
- Re: The SQL Server cannot obtain a LOCK resource at this time.
  - From: Hilary Cotter
- Re: The SQL Server cannot obtain a LOCK resource at this time.
  - From: \"akej via SQLMonster . com\"

Prev by Date: Re: Merge replication in 'SQL Server'
Next by Date: Re: Replication job does not end - even when its idle on the server
Previous by thread: Re: The SQL Server cannot obtain a LOCK resource at this time.
Next by thread: Re: The SQL Server cannot obtain a LOCK resource at this time.
Index(es):
- Date
- Thread