Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

managing replication

Status
Not open for further replies.

ProBani

Programmer
Mar 21, 2005
48
YU
hi all,

I want to enable replication between to servers A and B, A - is publisher/ditributor and B - is subsriber. The thing is that the online database is located in the server A. So, a don't want to replicate everrything on the server B, because I want to make the last backup from server A and restore it into, it means no neccessary inserting recorords that exists and structure that is already in the server B (through the restoring).

How is this possible, is there option when configuring subscriber ?? maybe ==>> ‘No, the Subscriber already has schema and data’ in the ‘Initialize Subscription’ screen of the subscription wizard.
But, after this I want all the cjanges in the server A to be replicated into the server B.

Regards,
ProBani.
 
Can anybody suggest on this? Because through the WAN to replicate all these data is too much, so I want to restore the last backup on the subscriber with all the data 'till that moment.

Rgds,
proBani.
 
You should have the choice when setting up your publication to have it send schema structure along with the data to Server B. Repliation can be weird, though, if it thinks it's sending over data that is already there. You could try using Row Filters if you can append a Date column to all your tables and fill it in with a GetDate() default. That way, only current information is repped over to Server B.



Catadmin - MCDBA, MCSA
"If a person is Microsoft Certified, does that mean that Microsoft pays the bills for the funny white jackets that tie in the back???
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top