Azure Sql Trigger could not found.

ghulam murtaza 0 Reputation points
2023-08-10T12:45:51.6666667+00:00

Hello Microsoft community,

I'm working on an Azure Function project (version 4) within an ASP.NET Core 6 application, and I'm utilizing the Microsoft.Azure.WebJobs.Extensions.Sql package (v2.0.144) to manage Azure SQL triggers. Unfortunately, I've encountered an issue where the SQL trigger does not seem to be functioning as expected.

I have verified that I'm using version 2.0.144 of the Microsoft.Azure.WebJobs.Extensions.Sql package, and my Azure Function is set to version 4. Additionally, I have checked my configuration to ensure that the connection string ("AzureWebJobsSqlConnection") is correctly set, and there don't appear to be any issues there.

Despite all of this, the trigger doesn't seem to work, and I'm not receiving any error messages to help diagnose the problem. Is there anything specific to Azure Function v4 or this version of the Microsoft.Azure.WebJobs.Extensions.Sql package that I should be aware of? Are there any compatibility issues or known bugs that could be causing this behavior?

Azure SQL Database
Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
5,685 questions
{count} votes

1 answer

Sort by: Most helpful
  1. MayankBargali-MSFT 70,891 Reputation points
    2023-08-11T05:26:32.1966667+00:00

    @ghulam murtaza Thanks for reaching out. As per your screenshot I can see the package was not found/installed properly or not supported as it is supported with .Net standard 2.0 or above version.

    https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-azure-sql-trigger?tabs=in-process%2Cportal&pivots=programming-language-csharp

    Please review the document here and readme for the Microsoft.Azure.WebJobs.Extensions.Sql package here. The sample can be found here. In case if you still observe the same behavior then please share the sample application so this can be reviewed further.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.