Split-merge tool still uses unsupported Classic Cloud Services

[mturzynskiaspire]

Classic Cloud Services will be retired August 2024. Could you please release the source code of this tool so that we can migrate on our own? It's getting quite urgent.

[stuartpa]

This is being investigated, can you give me some more details about your use case for this. We are looking at ways to move this solution forward to a more modern offering.

[mturzynskiaspire]

We've got around 60 shared databases that host multiple tenants each. We use split-merge-tool to move tenants across shards (databases) to ensure that the load is distributed evenly. There are thousands of tenants, some of them are really small. We can't design to use a single database per tenant as this would be unmaintanable.

[stuartpa]

Are you comfortable filing a support case? I'd like it to be immediately escalated to me in the product group. And you can reference this comment for clarity.

[mturzynskiaspire]

Are you comfortable filing a support case? I'd like it to be immediately escalated to me in the product group. And you can reference this comment for clarity.

Sure, the support case id is 2403080050002082. Thank you for your help, I appreciate that.

[QuintinKriek]

For what its worth, we have a similar scenario. Although we could get the service hosted in a "Cloud services (extended support)" instance, it still has a hard requirement of Azure Storage with TLS1.0, which will be removed 31 Oct 2024.

Any updates on this would be greatly appreciated

[EatMoreCookies]

Also wondering if there has been any progression on this issue? My company is looking to create this service to split data from a single DB to multiple.

My company is unable to use "Cloud services (extended support)" because of the type of our azure subscription and creating the split-merge service in the newer "Cloud Services" does not seem to have any documentation.

We will be forced to create our own tool if this service is not migrated (or source code released).

[QuintinKriek]

@stuartpa Any updates on this? As you can imagine, we would need to make provisions ahead of time if we need to develop our own tools to perform these tasks. (Ahead of the 31 Oct 2024 Azure TLS1.0 retirement issue)

Really hoping the source code (Or a new version) can be made public though.

Thanks

[calloncampbell]

Similar scenario. Any updates on this?