Azure SQL Trigger Function fails with exception: Invalid object name 'az_func.Leases_xxx_xxx' after function redeployment.

Question

Azure SQL Trigger Function fails with exception: Invalid object name 'az_func.Leases_xxx_xxx' after function redeployment.

Roman Skolin 20

I have an SQL Trigger Azure Function that is deployed to an Azure Function App as a container. The function image is stored in Azure Container Registry (ACR). All RBAC permissions (to pull from ACR, access the database, etc.) are correctly configured.

When I first start the function, it creates the table [az_func].[GlobalState] in the target database, as well as a lease table such as [az_func].[Leases_{FuncHash1}_{TableHash1}]. Everything works as expected at this stage.

The problem appears when I reinstall the function into the Function App. Essentially, I just swap the image tag in my ACR settings in the Function App Deployment Center and restart the Function App.

After this redeployment, I see an odd situation:

The function container starts up.

A new lease table is created, e.g. [az_func].[Leases_{FuncHash2}_{TableHash1}].

However, the Function App logs are filled with errors like:

[Error] Failed to check for changes in table 'Data.Trigger' (my CDC-enabled table)  
due to exception: Microsoft.Data.SqlClient.SqlException.  
Exception message: Invalid object name 'az_func.Leases_{FuncHash1}_{TableHash1}'.

So, instead of using the new lease table, the function continues to look for the old one from the previous deployment.

I have tried:

Rebuilding the image

Deleting the repository in ACR

Manually replacing the image tag with a specific version or using the generic latest

None of these helped. The function always throws the same exception:

Microsoft.Data.SqlClient.SqlException.  
Exception message: Invalid object name 'az_func.Leases_{FuncHash1}_{TableHash1}'.

The function detects changes in the CDC-enabled table but fails to process them, since it only looks for the old lease table and does not properly switch to the new one.

Any idea why this happens? I couldn’t find anything relevant in the documentation. I have an SQL Trigger Azure Function that is deployed to an Azure Function App as a container.

The function image is stored in Azure Container Registry (ACR). All RBAC permissions (to pull from ACR, access the database, etc.) are correctly configured.

When I first start the function, it creates the table [az_func].[GlobalState] in the target database, as well as a lease table such as [az_func].[Leases_{FuncHash1}_{TableHash1}]. Everything works as expected at this stage.

The problem appears when I reinstall the function into the Function App. Essentially, I just swap the image tag in my ACR settings in the Function App Deployment Center and restart the Function App.

After this redeployment, I see an odd situation:

The function container starts up.

A new lease table is created, e.g. [az_func].[Leases_{FuncHash2}_{TableHash1}].

However, the Function App logs are filled with errors like:

[Error] Failed

So, instead of using the new lease table, the function continues to look for the old one from the previous deployment.

I have tried:

Rebuilding the image

Deleting the repository in ACR

Manually replacing the image tag with a specific version or using the generic latest

None of these helped. The function always throws the same exception:

Microsoft.Data.SqlClient.SqlException.

The function detects changes in the CDC-enabled table but fails to process them, since it only looks for the old lease table and does not properly switch to the new one.

Any idea why this happens? I couldn’t find anything relevant in the documentation.

Praveen Kumar Gudipudi 160 Reputation points Microsoft External Staff

2025-08-28T04:49:50.5+00:00

Hello Roman Skolin,

Rebuilding the image, Deleting the repository in ACR, manually replacing the image tag.

These actions only impact the container itself. The lease table and GlobalState are external (in the SQL DB), so redeploying the container doesn't clean up or reset that external state.

Please Clean GlobalState on deployment if you want a clean start:

DELETE FROM [az_func].[GlobalState]- This clears the state and forces the function to start fresh with its new function hash and lease table.
Roman Skolin 20 Reputation points

2025-08-28T05:56:25.3633333+00:00
Hi, I also tried deleting all az_func schema tables including GlobalState, but this didn’t help. To be honest, our DevOps process drops and recreates the database in the middle of the night. This essentially deletes everything, and the function restart/reinitialization is also part of the DevOps process. If I stop my function app, delete az_func.GlobalState and az_func.Lease_{FuncHash1}_{TableHash1}, then I select a new container version and start the function app. New az_func tables are created according to the setup from my function. For example, if I hardcode a lease table name in my function, then a table with that name will be created in the database, like az_func.GlobalState + az_func.MyHardcodedLeaseTablename.

However, the Function App log stream keeps showing the following error:

Failed to check for changes in table 'Data.Trigger' due to exception: Microsoft.Data.SqlClient.SqlException. Exception message: Invalid object name 'az_func.Leases_{FuncHash1}_{TableHash1}'

It seems to be a configuration issue between the Function running in a container, the underlying App Service plan, and the database.

What’s also interesting is that I tried deploying not from the container, but directly into another Azure Function App Service from code, and everything works fine after the function restarts.
Roman Skolin 20 Reputation points

2025-08-28T07:24:25.3633333+00:00

Traces from the logstream:

on function app start:

DECLARE @last_sync_version bigint; SELECT @last_sync_version = LastSyncVersion FROM [az_func].[GlobalState] WHERE UserFunctionID = '6d9961d07365c556' AND UserTableID = 1957998452; IF @last_sync_version < @min_valid_version BEGIN UPDATE [az_func].[GlobalState] SET LastSyncVersion = @min_valid_version WHERE UserFunctionID = '6d9961d07365c556' AND UserTableID = 1957998452; SELECT 'Updated LastSyncVersion from ' + CAST(@last_sync_version AS NVARCHAR) + ' to ' + CAST(@min_valid_version AS NVARCHAR); END

and right under this trace -

2025-08-28T07:03:53Z [Error] Failed to check for changes in table 'Data.ADFTrigger' due to exception: Microsoft.Data.SqlClient.SqlException. Exception message: Invalid object name 'az_func.Leases_ca31cb488f250b65_1957998452'.

I have in my database table Leases_6d9961d07365c556_1957998452 after container start, but appservice insists on having az_func.Leases_ca31cb488f250b65_1957998452

Your answer

Praveen Kumar Gudipudi 160 Reputation points Microsoft External Staff

2025-08-28T04:49:50.5+00:00

Hello Roman Skolin,

Rebuilding the image, Deleting the repository in ACR, manually replacing the image tag.

These actions only impact the container itself. The lease table and GlobalState are external (in the SQL DB), so redeploying the container doesn't clean up or reset that external state.

Please Clean GlobalState on deployment if you want a clean start:

DELETE FROM [az_func].[GlobalState]- This clears the state and forces the function to start fresh with its new function hash and lease table.
Roman Skolin 20 Reputation points

2025-08-28T05:56:25.3633333+00:00

Hi, I also tried deleting all az_func schema tables including GlobalState, but this didn’t help. To be honest, our DevOps process drops and recreates the database in the middle of the night. This essentially deletes everything, and the function restart/reinitialization is also part of the DevOps process. If I stop my function app, delete az_func.GlobalState and az_func.Lease_{FuncHash1}_{TableHash1}, then I select a new container version and start the function app. New az_func tables are created according to the setup from my function. For example, if I hardcode a lease table name in my function, then a table with that name will be created in the database, like az_func.GlobalState + az_func.MyHardcodedLeaseTablename.

However, the Function App log stream keeps showing the following error:

Failed to check for changes in table 'Data.Trigger' due to exception: Microsoft.Data.SqlClient.SqlException. Exception message: Invalid object name 'az_func.Leases_{FuncHash1}_{TableHash1}'

It seems to be a configuration issue between the Function running in a container, the underlying App Service plan, and the database.

What’s also interesting is that I tried deploying not from the container, but directly into another Azure Function App Service from code, and everything works fine after the function restarts.
Roman Skolin 20 Reputation points

2025-08-28T07:24:25.3633333+00:00

Traces from the logstream:

on function app start:

DECLARE @last_sync_version bigint; SELECT @last_sync_version = LastSyncVersion FROM [az_func].[GlobalState] WHERE UserFunctionID = '6d9961d07365c556' AND UserTableID = 1957998452; IF @last_sync_version < @min_valid_version BEGIN UPDATE [az_func].[GlobalState] SET LastSyncVersion = @min_valid_version WHERE UserFunctionID = '6d9961d07365c556' AND UserTableID = 1957998452; SELECT 'Updated LastSyncVersion from ' + CAST(@last_sync_version AS NVARCHAR) + ' to ' + CAST(@min_valid_version AS NVARCHAR); END

and right under this trace -

2025-08-28T07:03:53Z [Error] Failed to check for changes in table 'Data.ADFTrigger' due to exception: Microsoft.Data.SqlClient.SqlException. Exception message: Invalid object name 'az_func.Leases_ca31cb488f250b65_1957998452'.

I have in my database table Leases_6d9961d07365c556_1957998452 after container start, but appservice insists on having az_func.Leases_ca31cb488f250b65_1957998452

Share via

Azure SQL Trigger Function fails with exception: Invalid object name 'az_func.Leases_xxx_xxx' after function redeployment.

Your answer