I have two SQL servers that I need to have the same. Synchronization should occur, maybe a couple of times a day, automatically. Both servers do not have a “direct” connection between them, so there are no related db, etc. (They are located on completely different computers, networks, domains, with firewalls in between). You can use the Internet, although, for example, a web service, FTP ...
CopyFromDB contains many tables, but only about 20 tables (only data, no schema changes at the moment) should be synchronized with CopyToDB. Only about half of the tables will have new / updated rows every day. The rest a couple of times a year. I guess this is only about a couple thousand lines a day right now. This may, however, grow in the future, up to about 100,000 lines per day. So there may not be too much data, I think.
And also (so far it can change) the data should be synchronized in only one direction - from CopyFromDB to CopyToDB. It would also be nice if it didn’t break just because someone adds an additional column to the table on CopyFromDB, but this new col should not be automatically synchronized with CopyToDB. (Only Cols that should be synchronized are on CopyToDB, there may be other columns that should not be synchronized)
It should do Insert, Update or Insert. In the worst case, I assume that this could lead to a complete deletion and insertion, but I don't like it. (There are FK courses, etc., so the data must be inserted in the correct order)
So far there is only one "CopyToDB", but this may increase. The solution should also be fairly simple and not too complicated .:-)
: ? .
- WS CopyToDB, CopyFromDB - ? .
- FTP CopyToDB, "sql" . //. CopyFromDB.
- - ? , ? 3d-? - Red Data SQL Data Compare, .
/ !
. , - "" , /. , , , ?:)