Publisher w/ 2 subscribers running merge replication.
the data was on all three machines and the i changed tables on the
publisher so the identity column was in a different range. i wanted it
to be an increment of 2 and a seed of 100,000, but instead i set an

I have got 2 publisher replicating to a subscriber
Publisher1 - Server1 / Db1
Publisher2 - Server2 / Db2
Subscriber - Server3 /Db3

Platform: 2 machines - Win2003 Server SP2 x64, SQL Server 2005
Problem: The subscriber is not being updated even though Replication Monitor
says Publication status is OK and Subscription Performance is Excellent.  It
was working fine for weeks and then just got stuck.  ...

MBT shoes are a kind of excellent barefoot healthy shoes. Due to MBT
shoes are slightly weighted and spread weight evenly across the entire
foot and as your body reacts to the weight and instability of the MBT
shoes’ sole, muscles, often the neglected muscles, are forced to work

We have customers that don't use replication, and some that use merge
replication.
I need a command able to be executed in a stored procedure that will
tell me is this SQL Server is a subscriber in a replication environment.