| Author | Stephen Bennett, sqlnotesfromtheunderground.wordpress.com |
| Availability | Windows, Linux, macOS |
Want to see the source code for this command? Check out Find-DbaAgentJob on GitHub.
Want to see the Bill Of Health for this command? Check out Find-DbaAgentJob.
Searches and filters SQL Agent jobs across SQL Server instances using multiple criteria.
Searches SQL Agent jobs across one or more SQL Server instances using various filter criteria including job name, step name, execution status, schedule status, and notification settings. Helps DBAs identify problematic jobs that have failed, haven't run recently, are disabled, lack schedules, or missing email notifications. Useful for maintenance audits, troubleshooting job issues, and identifying cleanup candidates in environments with many automated processes.
Find-DbaAgentJob
[-SqlInstance] <DbaInstanceParameter[]>
[[-SqlCredential] <PSCredential>]
[[-JobName] <String[]>]
[[-ExcludeJobName] <String[]>]
[[-StepName] <String[]>]
[[-LastUsed] <Int32>]
[-IsDisabled]
[-IsFailed]
[-IsNotScheduled]
[-IsNoEmailNotification]
[[-Category] <String[]>]
[[-Owner] <String>]
[[-Since] <DateTime>]
[-EnableException]
[<CommonParameters>]
PS C:\> Find-DbaAgentJob -SqlInstance Dev01 -JobName *backup*
Returns all agent job(s) that have backup in the name
PS C:\> Find-DbaAgentJob -SqlInstance Dev01, Dev02 -JobName Mybackup
Returns all agent job(s) that are named exactly Mybackup
PS C:\> Find-DbaAgentJob -SqlInstance Dev01 -LastUsed 10
Returns all agent job(s) that have not ran in 10 days
PS C:\> Find-DbaAgentJob -SqlInstance Dev01 -IsDisabled -IsNoEmailNotification -IsNotScheduled
Returns all agent job(s) that are either disabled, have no email notification or don't have a schedule. returned with detail
PS C:\> $servers | Find-DbaAgentJob -IsFailed | Start-DbaAgentJob
Finds all failed job then starts them. Consider using a -WhatIf at the end of Start-DbaAgentJob to see what it'll do first
PS C:\> Find-DbaAgentJob -SqlInstance Dev01 -LastUsed 10 -ExcludeJobName "Yearly - RollUp Workload", "SMS - Notification"
Returns all agent jobs that have not ran in the last 10 days ignoring jobs "Yearly - RollUp Workload" and "SMS - Notification"
PS C:\> Find-DbaAgentJob -SqlInstance Dev01 -Category "REPL-Distribution", "REPL-Snapshot" | Format-Table -AutoSize -Wrap
Returns all job/s on Dev01 that are in either category "REPL-Distribution" or "REPL-Snapshot"
PS C:\> Find-DbaAgentJob -SqlInstance Dev01, Dev02 -IsFailed -Since '2016-07-01 10:47:00'
Returns all agent job(s) on Dev01 and Dev02 that have failed since July of 2016 (and still have history in msdb)
PS C:\> Get-DbaRegServer -SqlInstance CMSServer -Group Production | Find-DbaAgentJob -Disabled -IsNotScheduled | Format-Table -AutoSize -Wrap
Queries CMS server to return all SQL instances in the Production folder and then list out all agent jobs that have either been disabled or have no schedule.
PS > $Instances = 'SQL2017N5','SQL2019N5','SQL2019N20','SQL2019N21','SQL2019N22'
Find-DbaAgentJob -SqlInstance $Instances -JobName backup -IsNotScheduled
Returns all agent job(s) wiht backup in the name, that don't have a schedule on 'SQL2017N5','SQL2019N5','SQL2019N20','SQL2019N21','SQL2019N22'
The target SQL Server instance or instances. You must have sysadmin access and server version must be SQL Server version 2000 or higher.
| Alias | |
| Required | True |
| Pipeline | true (ByValue) |
| Default Value |
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.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
Specifies agent job names to search for using exact matches or wildcard patterns.
Supports wildcards like backup, MyJob*, or ETL to find jobs with specific naming conventions.
Useful when you need to focus on particular job types or troubleshoot specific processes.
| Alias | Name |
| Required | False |
| Pipeline | false |
| Default Value |
Excludes specific job names from the search results using exact name matches.
Use this to filter out known good jobs when searching for problematic ones, like excluding maintenance jobs when looking for failed application jobs.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
Searches for jobs containing steps with specific names or patterns.
Supports wildcards to find jobs with steps like backup, index, or cleanup.
Helpful when troubleshooting issues in multi-step jobs or finding jobs that perform specific operations.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
Finds jobs that haven't executed successfully in the specified number of days.
Use this to identify stale or potentially broken jobs that may need attention.
Common values are 7, 30, or 90 days depending on job frequency and business requirements.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value | 0 |
Finds all jobs with disabled status (not scheduled to run automatically).
Use this during maintenance windows to identify jobs that were disabled for troubleshooting or may have been forgotten after maintenance.
| Alias | Disabled |
| Required | False |
| Pipeline | false |
| Default Value | False |
Finds jobs where the last execution resulted in a failure status.
Essential for daily health checks and identifying jobs that need immediate attention.
Combine with Since parameter to focus on recent failures or look at historical patterns.
| Alias | Failed |
| Required | False |
| Pipeline | false |
| Default Value | False |
Finds jobs that exist but have no schedule defined (manual execution only).
Useful for identifying orphaned jobs, temporary jobs that should be cleaned up, or jobs awaiting proper scheduling configuration.
| Alias | NoSchedule |
| Required | False |
| Pipeline | false |
| Default Value | False |
Finds jobs that lack email notification setup for failures or completion.
Important for ensuring critical jobs will alert DBAs when they fail.
Use this during compliance audits or when establishing monitoring standards.
| Alias | NoEmailNotification |
| Required | False |
| Pipeline | false |
| Default Value | False |
Filters jobs by their assigned categories such as 'Database Maintenance', 'REPL-Distribution', or custom categories.
Useful for focusing on specific types of jobs like replication jobs, maintenance tasks, or application-specific processes.
Categories help organize and manage jobs in environments with many different job types.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
Filters jobs by their owner login name, or excludes jobs by prefixing with a dash (-).
Use 'DOMAIN\User' to find jobs owned by specific accounts, or '-sa' to exclude sa-owned jobs.
Helpful for security audits, identifying jobs that may need ownership changes, or finding jobs created by specific users.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
Limits results to jobs that last ran on or after the specified date and time.
Use with IsFailed to find jobs that failed since a specific incident, or combine with other filters to focus on recent activity.
Accepts standard datetime formats like '2023-01-01' or '2023-01-01 14:30:00'.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value |
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.
| Alias | |
| Required | False |
| Pipeline | false |
| Default Value | False |