a***h
发帖数: 29 | 1 SQL Server数据同步复制
网上有一个SQL Server A. 每天晚上12点将数据复制到SQL Server
B中(此SQL Server与网上的那个SQL Server
A不在同一处,两者通过ISDN拨号相连). 要求: Server B 计算
Server A 一天来新增的数据, 并且将计算结果回写Server A.
请问: 应用Snapshot, Transcation,还是Merge 同步方式?
注意: 如果12:00时将 Server A 的数据载到 Server B, 当Server B
完成计算时可能已是2:00时了, Server A 的数据又有所更新, 这时
应如何将 Server B 的计算结果回写 Server A? | s****r
发帖数: 17 | 2 IMPO, should be Snapshot. When you write back data to
Server B, do you write to a new table in Server A?
【在 a***h 的大作中提到】
: SQL Server数据同步复制
: 网上有一个SQL Server A. 每天晚上12点将数据复制到SQL Server
: B中(此SQL Server与网上的那个SQL Server
: A不在同一处,两者通过ISDN拨号相连). 要求: Server B 计算
: Server A 一天来新增的数据, 并且将计算结果回写Server A.
: 请问: 应用Snapshot, Transcation,还是Merge 同步方式?
: 注意: 如果12:00时将 Server A 的数据载到 Server B, 当Server B
: 完成计算时可能已是2:00时了, Server A 的数据又有所更新, 这时
: 应如何将 Server B 的计算结果回写 Server A?
| a***h
发帖数: 29 | 3 Since Server A 托管了, so i want to refresh Server A via
Server B.
If i want to add new table, i may add it directly in Server
A, because
adding a new table is not a daily rutine. So, not need to
consider adding
a new table in Server A.
Why Snapshot? why not Merge?
【在 s****r 的大作中提到】
: IMPO, should be Snapshot. When you write back data to
: Server B, do you write to a new table in Server A?
| s****r
发帖数: 17 | 4 My first thought is that merge is more than you need. With
ISDN, I thought that snapshot will be more stable and
effecient.
But now I think that merge is probably a good choice because
it supports causal dial up connections.
【在 a***h 的大作中提到】
: Since Server A 托管了, so i want to refresh Server A via
: Server B.
: If i want to add new table, i may add it directly in Server
: A, because
: adding a new table is not a daily rutine. So, not need to
: consider adding
: a new table in Server A.
: Why Snapshot? why not Merge?
| a***h
发帖数: 29 | 5 but after one day running, Server A's record is different
from those of Server B
(we input data manualy into Server B). then, when using
snapshot, will Server A's record cover Server B's?
【在 s****r 的大作中提到】
: My first thought is that merge is more than you need. With
: ISDN, I thought that snapshot will be more stable and
: effecient.
: But now I think that merge is probably a good choice because
: it supports causal dial up connections.
| s****r
发帖数: 17 | 6 If A is the publisher and B is the subscriber, B's record
will not be write back to A by snapshot.
As far as I know, there are only 2 ways to write
subscriber's data back to publisher. One is merge and
another one is transactional with immediately updated
subscriber.
Using merge, we can decide the conflict resolution (whether
publisher or subscriber).
If merge supports dialup connectino well, then it is
absolutely a better choice. There is not much discussion
about this in BOL, but it is menti
【在 a***h 的大作中提到】
: but after one day running, Server A's record is different
: from those of Server B
: (we input data manualy into Server B). then, when using
: snapshot, will Server A's record cover Server B's?
| s****r
发帖数: 17 | 7 If A is the publisher and B is the subscriber, B's record
will not be write back to A by snapshot.
As far as I know, there are only 2 ways to write
subscriber's data back to publisher. One is merge and
another one is transactional with immediately updated
subscriber.
Using merge, we can decide the conflict resolution (whether
publisher or subscriber).
If merge supports dialup connectino well, then it is
absolutely a better choice. There is not much discussion
about this in BOL, but it is menti
【在 a***h 的大作中提到】
: but after one day running, Server A's record is different
: from those of Server B
: (we input data manualy into Server B). then, when using
: snapshot, will Server A's record cover Server B's?
| a***h
发帖数: 29 | 8 1.why you use transactional at 12:00am, and then still use
merge at 2:00?
2.in "backup-zip-ftp-unzip-restore" , "backup" means fully
backup the whole database? could you explain more about how
to do.
3. server A is in web site, server B is a POS, A receive
order from customer, and receive membership registration. we
input new product infomation into B. Every evening, two
server connect, A transmit order forms and membership info
to B, B transmit product infomation to A, and computer
A'data and t
【在 s****r 的大作中提到】
: If A is the publisher and B is the subscriber, B's record
: will not be write back to A by snapshot.
: As far as I know, there are only 2 ways to write
: subscriber's data back to publisher. One is merge and
: another one is transactional with immediately updated
: subscriber.
: Using merge, we can decide the conflict resolution (whether
: publisher or subscriber).
: If merge supports dialup connectino well, then it is
: absolutely a better choice. There is not much discussion
|
|
