Publisher, Distribution, Subscriber all on one SQL Server?

Should this work? In production we have one server acting as the
publisher/distributer, and then another as the subscriber.
In the test environment, I'd like to have all of this on the same
server. Will this work? I've run into what I hope is a minor gotcha
(running the drop replication scripts created by enterprise manager
doesn't work, exec sp_dropsubscription returns "The remote server is
not defined as a subscription server").
thanks for any hints.
Sylvia
Hey. I've the same setup at my company for testing. It works fine. I have 2
instances of SQL, one acting as a subscriber and the other acting as a
publisher/distributor for transactional and merge replication. I've 3
publications so far.
For your structure, how is it defined? On your publication, have you defined
the same server as a publisher as well as a subcriber?
|||I even do pull subscriptions using FTP on a single server.
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
"Sylvia" <sylvia@.vasilik.com> wrote in message
news:1130800544.680463.133070@.z14g2000cwz.googlegr oups.com...
> Should this work? In production we have one server acting as the
> publisher/distributer, and then another as the subscriber.
> In the test environment, I'd like to have all of this on the same
> server. Will this work? I've run into what I hope is a minor gotcha
> (running the drop replication scripts created by enterprise manager
> doesn't work, exec sp_dropsubscription returns "The remote server is
> not defined as a subscription server").
> thanks for any hints.
> Sylvia
>