Redian新闻
>
Do replicated tables need identical?
avatar
Do replicated tables need identical?# Database - 数据库
e*n
1
紧急求助:I485 pending 180 天,I140已批准且relink to I485 and under review.
现在要换新工作,需要transfer
I140? If yes, how to transfer?
Thank you very much for any input in advance!
avatar
l*b
2
Hi, friends,
In SQL server 2005, I have case to build new DB in another location and have replication with
existed DB. They have same schema. My approach is:
1. backup the existed DB, restore to new DB
2. delete some old data in new DB - existed DB keeps 10 years data, new DB
maintain the recent 3 year data.
3. make two DB replication in sync - bi-direction transactional or merge
type
Does this work in not-identical data DB replication?
Thank you
avatar
l*b
3
More, it is in SQL Server 2005
avatar
S*0
4
I have not used merge replication so far yet, but here is what I thought,
from the transactional replication standpoint, about your scenario, which
the publisher and subscriber are in different status.
1. Disable the Snapshot. During the replication configuration, you can
delay the snapshot, then even disable the snapshot job, so the snapshot will
never happen for this replication. This way, you can keep them in its own
status.
2. Another way is to use snapshot first, get both publisher a

【在 l*****b 的大作中提到】
: Hi, friends,
: In SQL server 2005, I have case to build new DB in another location and have replication with
: existed DB. They have same schema. My approach is:
: 1. backup the existed DB, restore to new DB
: 2. delete some old data in new DB - existed DB keeps 10 years data, new DB
: maintain the recent 3 year data.
: 3. make two DB replication in sync - bi-direction transactional or merge
: type
: Does this work in not-identical data DB replication?
: Thank you

相关阅读
logo
联系我们隐私协议©2024 redian.news
Redian新闻
Redian.news刊载任何文章,不代表同意其说法或描述,仅为提供更多信息,也不构成任何建议。文章信息的合法性及真实性由其作者负责,与Redian.news及其运营公司无关。欢迎投稿,如发现稿件侵权,或作者不愿在本网发表文章,请版权拥有者通知本网处理。