January 23, 2008 at 1:36 pm
We need to maintain replicated subscriber data. Here is what I am trying to do in SS 2005:
Have replication setup, with the subscriber not receiving DELETE transactions, and have no snapshot initialization (the first initialization of the subscriber DB would of course be from a backup of the publisher). With the subscriber NOT receiving DELETE transactions, it will be in a sense the archive DB. Problem comes when we have issues and need to reinitialize the subscriber DB. We wouldn't be able to use the publisher backup since it will not have all of the archived data. Can we reinitialize the subscriber DB from a backup of itself instead of the publisher?
Thanks in advance,
Matt F.
January 29, 2008 at 11:28 pm
To my uinderstanding i dont think its possible, though a workaround solution if u like
in delete procedure put a command to move records to a new archive database and then let it get deleted from subscriber, rather than keeping in same database, and then create a view on top of it...
Prakash Heda
Lead DBA Team - www.sqlfeatures.com
Video sessions on Performance Tuning and SQL 2012 HA
May 2, 2008 at 5:09 pm
Did you end up finding out a way to accomplish this? I was my understanding that one could restore from backups instead of snapshots, but every time I try and do this using a different db backup (besides the publishers) it complains about having incorrect headers.
I have one scenario where I need an archival db where all of the deletes are disregarded during replication (sp_MSdel_dbotablename altered to return 1) and another where the updates' stored procedures are totally customized to allow alternate id's (keeping the same primary key) and conversions. It's not hard to start the initial replication but I'm unsure how to reinitialize the replication once the subscribers datasets vary so wildly away from the publishers.
I've read that this can be done using:
Execute sp_replicationdboption ' ', 'sync with backup', 'true'
and
use X
GO
exec sp_addsubscription
@publication = N'Replication',
@subscriber = N'HQ15',
@destination_db = N'W',
@subscription_type = N'Push',
@sync_type = N'none',
@article = N'all',
@update_mode = N'read only',
@subscriber_type = 0
and then rerunning the altered stored procedures. Anyone know of a good walk through of how to script all aspects of a replication?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply