-
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
Support multi-catalog deployments #149
Comments
As discussed this morning the |
Should support both: |
I am not convinced here. Single even SQL 2016 does not support cross-catalog transactions in AlwaysOn mode, catalog seems to be something physical rather than logical. I'd rather put the catalog/database in same bucket as SQL server instances and handle it similarly to RabbitMQ shovel plugin. |
@SzymonPobiega here you are sir #146 And you have a good point, @tmasternak let's review this in light of that. |
Here's the article that describes AlwaysOn vs cross-catalog transactions: https://technet.microsoft.com/en-us/library/ms366279(v=sql.130).aspx. My understanding is |
I think that we should try a spike and verify our assumptions. |
Spike issue has been created: #325. |
Fixed by #330 |
Version 3 of SqlTransprort supports only multi-schema setup. It should be possible to add multi-catalog support as well.
See #139 for more details
Inception: https://github.com/Particular/CustomerSuccess/issues/166
The text was updated successfully, but these errors were encountered: