I seem to have big difficulties setting up the first replication ever between two SQL2000 instances.
They both run in seperate WAN's (IP with port assigned for SQL-remote) but I have been able to connection them through remote-SQL so they appear in Enterprise Manager in both places.
I cant figure out how to do this correctly, as I have tried many different approaches and got a lot of errors trying to do it.
I dont know if its a faulty installation (with SP4) or some rights I need to ajust or what I am trying to do isnt possible.
My idea is to take the primary server (lets call it MASTER or #5) and then PUBLISH some of its databases with replication to the secondary/backup server (lets call it SLAVE or #4)
I've added a "sync account login" on both, with same name and password to see if that would make things easier. I have FULL administrative access, so any needed changes can be made to this setup - as long as I get it fixed soon. (Have been starting to consider leaving SQL-server completely if this has to take so long time to fix, and check out MySQL or something else)...
BUT... to the current task/situation:
We have two servers, one in production and one in development, and I would REALLY like to have changes MERGE between these two "single instances". There is NO ActiveDirectory mechanism near them, so they are 100% stand-alone machines.
When I try to configure the master as "Distributor/Publisher" the Wizard halts with error of something being "(null)" ??? I get some weird error codes that tells me nothing usefull.
So I was wondering, is there a "guided tour" somewhere on HOW to do this in the right order, so that I can check if I have missed something before trying to set it up. Some rights, some flags, some patches or extra firewall ports or something weird needed for replication.
It looks so easy in every example I have found so far, but it just doesnt work ...
HELP!... please :-)
To get replication running between two servers which aren't on the same domain, you'll need to do one of the following.
After that each machine should be able to access the other via the local name which is required for replication to work. Once name resolution is working ok you should be able to just run through the wizard to get things setup.
Now keep in mind that it is usually recommended to not replicate data between production and dev, especially with merge replication as any changes made in your development environment will be replicated to the production database.
Also keep in mind that once you replicate a table you can't make any schema changes to those tables using the normal ALTER TABLE commands. You'll have to use the replication procedures to add columns. Another catch is that SQL 2000 replication will be adding a guid column to every table that you are replicating.
Where is the process breaking? Are you able to get the distributor setup?