Extension does not support cross-region failover

[manijndl]

• Azure Functions SQL Extension or Extension Bundle Version:
• Is this a deployed or local function: 2 local functions having same name (later we will leverage if fits our use case)
• What type of Database are you using? (Run SELECT @@VERSION as Version, SERVERPROPERTY('EngineEdition') as EngineEdition on your database)

Microsoft SQL Azure (RTM) - 12.0.2000.8 Oct 2 2024 11:51:41 Copyright (C) 2022 Microsoft Corporation |   -- | --

- List any custom settings for your function app. This could be a custom time-out defined specifically for your database server or optional configuration that can be customized for the app defined [here](https://learn.microsoft.com/azure/azure-functions/functions-bindings-azure-sql-trigger?tabs=isolated-process%2Cportal&pivots=programming-language-csharp#optional-configuration).

Issue Description: -

1. We are internal Microsoft team trying to leverage SQL Trigger if we will deploy SQL Trigger to different regions suppose eastus, westus for region fail over scenarios in that case there is no way there change logs will be mutually exclusive and if one function goes down other will continue from the same point. can you please suggest some way out for this. if we deploy it in two diff regions it will result in duplicate records.

[amaraslam07]

I also have a use case of running the function app with SQL trigger in multi region environment.

I reviewed the leases table concepts and tested it locally.

It appears that scalability functions well in a single region when auto-scaling is enabled for the Function App. The reason for this is that the UserFunctionId in az_func.GlobalState table is generated based on the read-only WEBSITE_SITE_NAME app setting of the Function App. Since this app setting is read-only, we cannot update the site name in the secondary region.

I confirmed this behavior by running functions locally with the same WEBSITE_SITE_NAME property for both processes. It only triggered one process at a time.

Is there any workaround for a multi-region active-active setup? This setup would be a requirement for many organizations ?