Central Subscriber Replication -
05-10-2006
, 03:50 PM
Good Afternoon Everyone!
I'm working on a project where I need to basically combine 8 servers' information into one server. There are two tables "table 1" and "Table 2" on all 8 servers, and I need to make a giant table 1 and a giant table 2 that houses data from all 8 servers.
I've been looking up replication for some time and I'm having the worst of luck. I'm not a DBA, so maybe that's why, but we work with a lot of databases, it's just that we don't really do any major TSQL kind of things, just DTS packages really.
Anyway, I'm talking about 2 different tables, each with about 30 columns and maybe 800-900 records a day per server, and we have 8 servers whose data we need to merge. Is this something that replication is good for? I'm looking at the model where there are multiple publishers and a central subscriber.
I'm having the hardest time setting this up. I think I got a pull subscription to work on the central table for one publisher, but when I tried to do it for a second table, I get this error:
Subscription 'ServerName:rplTest' cannot be reinitialized automatically because it was initialized manually when it was created. To reinitialize this subscription, you must drop and recreate it.
The reason I'm trying to reinitialize this is because if I make changes to the first one and choose to reinitialize the subscription, the next time I restart the SnapShot Agent, it'll update the my table in the rplTest database on the central server. I can't get the updates from my second server, so that's why I try to reinitialize it.
Any insight would be GREATLY appreciated!
Last edited by bkbroiler2k : 05-10-2006 at 04:04 PM
.
|