search

Particular / NServiceBus.SqlServer

SQL Server Transport for NServiceBus
https://docs.particular.net/nservicebus/sqlserver/
Other
42 stars 35 forks source link

Support multi-catalog deployments #149

Closed tmasternak closed 6 years ago

tmasternak commented 8 years ago

Version 3 of SqlTransprort supports only multi-schema setup. It should be possible to add multi-catalog support as well.

See Particular/NServiceBus.SqlServer#139 for more details Inception: https://github.com/Particular/CustomerSuccess/issues/166

mauroservienti commented 8 years ago

As discussed this morning the catalog name should be part of the endpoint address as it is for the schema name in 3.0

ramonsmits commented 8 years ago

Should support both: userdb.dbo and also [userdb].[dbo] to also supports dots in catalogs and/or schemas.

SzymonPobiega commented 8 years ago

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.

mauroservienti commented 8 years ago

@szymonpobiega here you are sir https://github.com/Particular/NServiceBus.SqlServer/issues/146

And you have a good point, @tmasternak let's review this in light of that.

SzymonPobiega commented 8 years ago

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 not supported but the wording is a bit confusing. Should we try it and verify?

tmasternak commented 8 years ago

I think that we should try a spike and verify our assumptions.

MarcinHoppe commented 7 years ago

Spike issue has been created: #325.

SzymonPobiega commented 7 years ago

Fixed by #330