Simone Bizzotto

well, it's a limitation. documenting that it works if your jobs are cmdexec type would clarify the limits, adjusting the code to use the current if cmdexec and develop a...

I concur. this is a request for documenting the limitation and optionally a feature request to make it digest the newer format.

looking at it it may be the null scrubber code that needs to be adapted https://github.com/dataplat/dbatools/blob/development/internal/functions/Invoke-DbaAsync.ps1#L125

ahum, that kb links https://download.microsoft.com/download/1/7/c/17c5d1d2-726c-4c62-868c-2b1c7f34636e/SQLServer2016-KB5006943-x64.exe so I don't get why is that a problem. One thing is knowing what release/sp/kb level you're on, the other is fetching the aforementioned "setup.exe"

 ?

nope but .... https://github.com/PowerShell/PowerShell/issues/11616

I'd say maintaining "what is downloadable" vs "what is not downloadable" is too much of a hassle. IMHO this should be closed as "wontfix".

The problem is that you're trying to execute a script rather than a query (and a rather complex one, as it needs to discern nested commands, and "GO" doesn't mean...

mmhh, try ExecuteNonQuery since I think your script doesn't return results. I don't think those are documented (except if you look at the help from Connect-DbaInstance) as they're not managed...

hum . wasn't your error related to executing something like ``` EXEC procedure_to_add_job @job_name=N'Job', @category_name=N'category', @anothersetting, @athirdsetting, @command=N'SELECT * FROM TableOne; GO; SELECT * FROM TableTwo;'" ``` that shouldn't be...