Merge pull request #260028 from JetterMcTedder/patch-1

update docs to use host.json

Author: prmerger-automator[bot]

articles/azure-functions/functions-bindings-azure-sql-trigger.md

@@ -514,17 +514,16 @@ The following table explains the binding configuration properties that you set i
 
 ## Optional Configuration
 
-In addition to the required ConnectionStringSetting [application setting](./functions-how-to-use-azure-function-app-settings.md#settings), the following optional settings can be configured for the SQL trigger:
+The following optional settings can be configured for the SQL trigger:
 
-| App Setting | Description|
+[!INCLUDE [app settings to local.settings.json](../../includes/functions-host-json-section-intro.md)]
+
+| Setting | Description|
 |---------|---------|
 |**Sql_Trigger_BatchSize** |The maximum number of changes processed with each iteration of the trigger loop before being sent to the triggered function. The default value is 100.|
 |**Sql_Trigger_PollingIntervalMs**|The delay in milliseconds between processing each batch of changes. The default value is 1000 (1 second).|
 |**Sql_Trigger_MaxChangesPerWorker**|The upper limit on the number of pending changes in the user table that are allowed per application-worker. If the count of changes exceeds this limit, it might result in a scale-out. The setting only applies for Azure Function Apps with [runtime driven scaling enabled](#enable-runtime-driven-scaling). The default value is 1000.|
 
-
-[!INCLUDE [app settings to local.settings.json](../../includes/functions-app-settings-local.md)]
-
 ## Set up change tracking (required)
 
 Setting up change tracking for use with the Azure SQL trigger requires two steps.  These steps can be completed from any SQL tool that supports running queries, including [Visual Studio Code](/sql/tools/visual-studio-code/mssql-extensions), [Azure Data Studio](/azure-data-studio/download-azure-data-studio) or [SQL Server Management Studio](/sql/ssms/download-sql-server-management-studio-ssms).