-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spike for multi-db support using merge replication #103
Comments
//cc: @tmasternak @SzymonPobiega @andreasohlund @mauroservienti Feel free to clarify if I forgot sth. |
I have just watched the meeting regarding this and I wonder if we jumping too quickly to a solution ? |
@johnsimons Do you have some alternatives in mind? I thought that this suggestion is based on previous discussions (e.g. from Budapest), so seemed like it's well thought ;) |
I think we can close this. Merge replication will not suit our goals as it does not have a transactional behavior. The synchronization between db's is performed is scheduled by external agent. /cc: @mauroservienti @weralabaj |
agree to close |
Connects to #100
Goal:
Use merge replication to provide multi-database support for SqlTransport.
https://msdn.microsoft.com/en-us/library/ms152746.aspx
https://technet.microsoft.com/en-us/library/ms151819(v=sql.105).aspx
Expected outcomes:
Timebox:
(days, people-days, deadline for presenting results?)
How about let's meet next Monday and see what we got by then?
The text was updated successfully, but these errors were encountered: