distrib.exe taking 100% of CPU

Hi,
I have bidirectional replication configured between 3 servers. Server A as
the distributor and publisher.
1. I have A publish to B and C.
2. A subcribes to B and C (push to A from B and C)
3. B publishes to and subscribes only to A. (push to A from B)
4. C publishes to and subscribes only to A. (push to A from C)
When I fire a transaction on A that includes several tables, I am getting
locking on 2 tables and the distrib.exe process runs continuosly and cannot
stop it from the task manager.
Any Ideas anyone?
AL
did you set loopback_detection=true?
"AL_LONGO" <AL_LONGO@.discussions.microsoft.com> wrote in message
news:FA5FA7A3-C8E9-4701-B3FC-60227A1B1EE6@.microsoft.com...
> Hi,
> I have bidirectional replication configured between 3 servers. Server A as
> the distributor and publisher.
> 1. I have A publish to B and C.
> 2. A subcribes to B and C (push to A from B and C)
> 3. B publishes to and subscribes only to A. (push to A from B)
> 4. C publishes to and subscribes only to A. (push to A from C)
> When I fire a transaction on A that includes several tables, I am getting
> locking on 2 tables and the distrib.exe process runs continuosly and
> cannot
> stop it from the task manager.
> Any Ideas anyone?
> AL
>
|||Hilary,
Yes, I used scripts to setup replication and double checked and it is in
fact there.
Any Ideas?
AL
"Hilary Cotter" wrote:

> did you set loopback_detection=true?
> "AL_LONGO" <AL_LONGO@.discussions.microsoft.com> wrote in message
> news:FA5FA7A3-C8E9-4701-B3FC-60227A1B1EE6@.microsoft.com...
>
>
|||Yes!
Any other Ideas?
AL
"Hilary Cotter" wrote:

> did you set loopback_detection=true?
> "AL_LONGO" <AL_LONGO@.discussions.microsoft.com> wrote in message
> news:FA5FA7A3-C8E9-4701-B3FC-60227A1B1EE6@.microsoft.com...
>
>
|||can you run profiler to see what is going on. Sometimes the distrib.exe will
cause high cpu utilization on initialization, but normally this is
transitory. There have been reports that it can be solved by a reboot.
"AL_LONGO" <ALLONGO@.discussions.microsoft.com> wrote in message
news:FEB163AA-579D-4136-8270-7CA671AE920C@.microsoft.com...[vbcol=seagreen]
> Hilary,
> Yes, I used scripts to setup replication and double checked and it is in
> fact there.
> Any Ideas?
> AL
> "Hilary Cotter" wrote:

distinguish between the Publisher and the Subscribers

I have a database on SQL Sever 2005 SP1 against which a Publication has been defined and to which many servers (both Workgroup and Express editions - SP1) Subscribe to.

I would like to be able to distinguish between the Publisher and the Subscribers programmatically via T-SQL.

From reading BoL and various forums it appears that the IsPublished, IsMergePublished and IsSubscribed options of the DatabasePropertyEx function should give me this information.

However within all our tested environments, whilst the IsMergePublished option returns expected values. IsPublished and IsSubscribed both return 0 on all servers (the Publisher and Subscribers).

Is this a know issue and how can I rectify the problem or alternatively does anyone know of another method to distinguishing between the Publishers and Subscribers.

Thanks

Hi Steve,

From BOL, IsPublished means "The tables of the database can be published for snapshot or transactional replication, if replication is installed.". So if your publication DB has merge publication, this value should be 0.

For IsSubscribed, looks like it is a documentation bug. I will open a bug for it.

Peng

|||Query distribution.dbo.MSmerge_subscriptions to find the subscribers. and distribution.dbo.MSpublications to find the publishers.