December 1, 2010 at 7:14 am
Is it possible to exclude deletes from your primary database with LOG SHIPPING ?
Expl: I have 2 databases: DB1 on server1 and DB2 on server2. I want to keep the two databases in sync, but DB1 contains data of 1 day to 3 months old and DB2 contains data of 1 day to 2 years old.
Thanks,
Douwe (The Netherlands)
December 1, 2010 at 7:29 am
No. when you ship the logs, you ship all modifications that were made.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 1, 2010 at 7:30 am
douwe.rijpsma (12/1/2010)
Is it possible to exclude deletes from your primary database with LOG SHIPPING ?Expl: I have 2 databases: DB1 on server1 and DB2 on server2. I want to keep the two databases in sync, but DB1 contains data of 1 day to 3 months old and DB2 contains data of 1 day to 2 years old.
Thanks,
Douwe (The Netherlands)
which is your primary database and which one is secondary. In log shipping, you cannot exclude anything. Whatever happens in primary will be applied in secondary and both will be in sync.
December 7, 2010 at 10:08 pm
Gail and Pradeep are correct.
For your situation, you'd likely want to look toward replication, and you can exclude deletes within the configuration of the publication. It's more involved to configure, but you can get as granular as you like with what data you want and where.
Regards,
Steve
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply