Open satory-sky opened 4 years ago
This driver does not yet support high-availability or failover options. It makes sense to consider those and any help is appreciated to get this featured in soon.
SQL Server AlwaysOn relies on instance resolution which requires #129 first to be in place. It makes sense to combine server resolution with the application intent (read only, read write) in some sense to cater for read-write and read-only nodes.
Hi
Is there any update on this topic? We are using this driver, but now we need support for MultiSubnetFailover and we would need to give up it if it is not supported. Can I somehow help, so we get support for MultiSubnetFailover?
Best, Milivoje
Hi
Could you please introduce MultiSubnetFailover parameter for r2dbc-mssql driver. I am considering to move from plain JDBC driver (that successfully supports MultiSubnetFailover) to R2DBC for mssql. However, I could not find any information regarding usage of MultiSubnetFailover parameter neither in documentation no in code. Do you have any plans to introduce this parameter as potential feature for a future release? Could you please help.
Best Regards, Alex Kontarero.