Spike for multi-db support using merge replication

[weralabaj]

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:

• Easier configuration for SqlTransport
• Safer connection management (connections shared for reading, not writing to another db)
• Making transport less smart than it is now (smart transports caused us trouble already)
• Works with SC and is backwards compatible (v1, v2)
• If necessary, define what tools we'd need to provide (e.g. scripts, docos, etc.)

Timebox:
(days, people-days, deadline for presenting results?)
How about let's meet next Monday and see what we got by then?

[weralabaj]

//cc: @tmasternak @SzymonPobiega @andreasohlund @mauroservienti Feel free to clarify if I forgot sth.

[johnsimons]

I have just watched the meeting regarding this and I wonder if we jumping too quickly to a solution ?

[weralabaj]

@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 ;)
Either way, please share your thoughts!

[tmasternak]

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

[mauroservienti]

agree to close