Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Could the disconnected database be updated? Expand / Collapse
Author
Message
Posted Tuesday, February 12, 2013 1:12 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, August 15, 2014 2:40 AM
Points: 207, Visits: 166
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.
Post #1418783
Posted Tuesday, February 12, 2013 1:37 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 6:20 AM
Points: 5,218, Visits: 5,067
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.





Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1418793
Posted Tuesday, February 12, 2013 1:55 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, August 15, 2014 2:40 AM
Points: 207, Visits: 166
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!
Post #1418799
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse