Add-AzSqlElasticJobStep missing parameter -MaxParallelism

[artisticcheese]

Description

Per this document (https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/sql-database/elastic-jobs-overview.md) you are expected to pass -MaxParallelism to limit concurrency. This parameter does not exists for Add-AzSqlElasticJobStep module

Steps to reproduce

Add-AzSqlElasticJobStep -MaxParallelism

Module versions

PS C:\Users\174181> get-installedmodule az.sql

Version              Name                                Repository           Description 
-------              ----                                ----------           -----------
1.14.0               Az.Sql                              PSGallery            Microsoft Azure PowerShell - SQL service cmdlets for Azure Resource Manager in Windows PowerShell and PowerShell Core.…   

[cormacpayne]

@jaredmoo @johnpaulkee Hey guys, would you mind taking a look at this issue?

[internetgdl]

In SQL Azure the capability of the number of threads are managed by Azure. Al least in this version of the az.sql module

[jaredmoo]

Thank you for reporting this issue. There is currently only T-SQL support for the max parallelism feature. This is of course a manageability gap that should be addressed. For now I will update the docs to eliminate the confusion.

[harshan007]

@jaredmoo @johnpaulkee Do we have update on adding this support in PowerShell? I see in documentation that its supported in powershell.
We have built powershell scripts to auto-manage database schema migrations and integrated it with our devops release pipeline and would be great to have this supported to avoid eating up azure DB DTUs during schema migration step.

https://docs.microsoft.com/en-us/azure/azure-sql/database/elastic-jobs-overview#agent-performance-capacity-and-limitations

[andyr8939]

Not ideal but I was able to get around this by doing the following with Powershell, to execute T-SQL on the steps I wanted to parallelize.

$setParallelQuery = @'
EXEC jobs.sp_update_jobstep
    @job_name = 'Daily-Maintainance-Job',
    @step_name = 'ExecuteMaintScript',
    @max_parallelism =  1
'@

Invoke-Sqlcmd -ServerInstance mytestsql.database.windows.net -Database elastic_job_database -Username mysqladmin -Password $sqladmin -OutputSqlErrors $true -Query $setParallelQuery

Obviously replace the server, database, user and password details etc, and then update the query to have the correct job and step name you need, but it should work after that. I have this step running when I create my elastic agent jobs to parallelize the steps I need to and it works fine for me.