Get-DbaRunningJob

Want to see the source code for this command? Check out Get-DbaRunningJob on GitHub.
Want to see the Bill Of Health for this command? Check out Get-DbaRunningJob.

Synopsis

Returns all non-idle Agent jobs running on the server

Description

This function returns agent jobs that active on the SQL Server instance when calling the command

Syntax

Get-DbaRunningJob
    [[-SqlInstance] <DbaInstanceParameter[]>]
    [[-SqlCredential] <PSCredential>]
    [[-InputObject] <Job[]>]
    [-EnableException]
    [<CommonParameters>]

Examples

Example: 1

PS C:\> Get-DbaRunningJob -SqlInstance sql2017

Returns any active jobs on sql2017

Example: 2

PS C:\> Get-DbaAgentJob -SqlInstance sql2017, sql2019 | Get-DbaRunningJob

Returns all active jobs on multiple instances piped into the function.

Example: 3

PS C:\> $servers | Get-DbaRunningJob

Returns all active jobs on multiple instances piped into the function.

Optional Parameters

-SqlInstance

The target SQL Server instance or instances

-SqlCredential

Login to the target instance using alternative credentials. Accepts PowerShell credentials (Get-Credential).
Windows Authentication, SQL Server Authentication, Active Directory - Password, and Active Directory - Integrated are all supported.
For MFA support, please use Connect-DbaInstance.

-InputObject

Enables piped input from Get-DbaAgentJob

-EnableException

By default, when something goes wrong we try to catch it, interpret it and give you a friendly warning message.
This avoids overwhelming you with "sea of red" exceptions, but is inconvenient because it basically disables advanced scripting.
Using this switch turns this "nice by default" feature off and enables you to catch exceptions with your own try/catch.