February 12, 2013 at 1:12 am
Colleagues,
I am in a bad need for ideas.
The situation looks like that. We (my company) have Server A which runs "A database". We want to (constantly) ship some changes made in it to the "B database" on Server B under following conditions:
1. We do not manage Server B. It is outside of our network. More, it is not and will never be directly connected to the Internet. It could however be connected to the Internet gateway, Server G.
2. "B database" is the subset of "A database". We want to give away some (not all!) tables as a whole and some (not all!) records in other tables. We must not give away some data from A. The backup files are out of questions. Or are they?
The ideal solution would be something like that:
Make a "magical artifact" on Server A, transfer it via the Internet to the Server G, get it from Server G and apply on Server B.
The problem is that I cannot imagine what the "magical artifact" should look like. It cannot be a database backup. Looks like it cannot be a replication snapshot. What other options do we have?
I appreciate any comments, questions, answers or (especially) suggestions.
February 12, 2013 at 1:37 am
Replicate into another database on ServerA the data that you want to send.
Back it up, send it to ServerG for ServerB to see, then do regular transaction log backups and have them shipped to ServerG and apply them to ServerB.
February 12, 2013 at 1:56 am
anthony.green (2/12/2013)
Replicate into another database on ServerA the data that you want to send.Back it up, send it to ServerG for ServerB to see, then do regular transaction log backups and have them shipped to ServerG and apply them to ServerB.
Ingenious.
I am really impressed.
Yes, that definitely would work.
Thank you very much!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply