Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit 18f611c

Browse files
authored
Merge pull request #21927 from LitKnd/elastic
Elastic jobs: correct code sample syntax and update limitations
2 parents e538c92 + 7fd29db commit 18f611c

2 files changed

Lines changed: 4 additions & 3 deletions

File tree

azure-sql/database/elastic-jobs-overview.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.topic: conceptual
1010
author: srinia
1111
ms.author: srinia
1212
ms.reviewer: kendralittle, mathoma
13-
ms.date: 12/18/2018
13+
ms.date: 05/03/2022
1414
---
1515
# Create, configure, and manage elastic jobs (preview)
1616
[!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
@@ -81,6 +81,7 @@ These are the current limitations to the Elastic Jobs service. We're actively w
8181
| :---- | :--------- |
8282
| The Elastic Job agent needs to be recreated and started in the new region after a failover/move to a new Azure region. | The Elastic Jobs service stores all its job agent and job metadata in the jobs database. Any failover or move of Azure resources to a new Azure region will also move the jobs database, job agent and jobs metadata to the new Azure region. However, the Elastic Job agent is a compute only resource and needs to be explicitly re-created and started in the new region before jobs will start executing again in the new region. Once started, the Elastic Job agent will resume executing jobs in the new region as per the previously defined job schedule. |
8383
| Concurrent jobs limit. | Currently, the preview is limited to 100 concurrent jobs. |
84+
| Excessive Audit logs from Jobs database | The Elastic Job agent operates by constantly polling the Job database to check for the arrival of new jobs and other CRUD operations. If auditing is enabled on the server that houses a Jobs database, a large amount of audit logs may be generated by the Jobs database. This can be mitigated by filtering out these audit logs using the `Set-AzSqlServerAudit` command with a predicate expression.<BR/><BR/>For example:<BR/> `Set-AzSqlServerAudit -ResourceGroupName "ResourceGroup01" -ServerName "Server01" -BlobStorageTargetState Enabled -StorageAccountResourceId "/subscriptions/7fe3301d-31d3-4668-af5e-211a890ba6e3/resourceGroups/resourcegroup01/providers/Microsoft.Storage/storageAccounts/mystorage" -PredicateExpression "database_principal_name <> '##MS_JobAccount##'"`<BR/><BR/>This command will only filter out Job Agent to Jobs database audit logs, not Job Agent to any target databases audit logs.|
8485

8586
## Best practices for creating jobs
8687

azure-sql/database/elastic-jobs-tsql-create-manage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.topic: how-to
1212
author: srinia
1313
ms.author: srinia
1414
ms.reviewer: kendralittle, mathoma
15-
ms.date: 02/01/2021
15+
ms.date: 05/03/2022
1616
---
1717
# Use Transact-SQL (T-SQL) to create and manage Elastic Database Jobs (preview)
1818
[!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
@@ -243,7 +243,7 @@ SELECT @poolEndTime = dateadd(minute, -30, @endTime)
243243
SELECT elastic_pool_name , end_time, elastic_pool_dtu_limit, avg_cpu_percent, avg_data_io_percent, avg_log_write_percent, max_worker_percent, max_session_percent,
244244
avg_storage_percent, elastic_pool_storage_limit_mb FROM sys.elastic_pool_resource_stats
245245
WHERE end_time > @poolStartTime and end_time <= @poolEndTime;
246-
'),
246+
',
247247
@credential_name = 'job_credential',
248248
@target_group_name = 'ElasticJobGroup',
249249
@output_type = 'SqlDatabase',

0 commit comments

Comments
 (0)