December 23, 2005 at 8:06 am
Hi
Here's my scenario...
A central SQL Server 2000 hosting several databases for different customers (one DB per customer).
Each customer has one or more MSDE databases on their own site(s) which each pull a subscription (one publication per customer) from the central SQL Server.
Each MSDE connects to the central SQL Server over a VPN.
The central SQL Server is part of our domain but the MSDEs are not part of our domain (they may be in their own domain or not in a domain at all).
Security must be such that no customer can subscribe to another's publication.
I would prefer to use IP addresses to name servers.
I've tried all sorts of configurations but I just can't get it working. The most frequent problem I hit is
'The remote server does not exist or has not been designated as a valid Publisher'
I've read snippets here and there regarding aliases etc, but I can't seem to find a definitive guide to setting up replication in the way described above.
Any ideas?
Thanks
January 4, 2006 at 2:05 pm
A few glitches I encountered (as best I can recall)
1. When referencing the remote server, don't use the DNS or "common name" of the remote server. For example, within our domain, we refer to our remote server as RemoteDB, but the actual name of the server is RemoteSQL. I had to log onto the local server directly (or remote desktop) in order to set up replication to "RemoteSQL".
2. I couldn't set up a pull subscription on "RemoteSQL", I needed to create a push subscription on "LocalDB" .
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply