Get-DbaAgentJobCategory View Source Sander Stad (@sqlstad), sqlstad.nl Windows, Linux, macOS Synopsis Retrieves SQL Server Agent job categories with usage counts and filtering options
Description Returns SQL Server Agent job categories from one or more instances, showing how many jobs are assigned to each category. Job categories help organize and group related SQL Agent jobs for easier management and reporting. This function retrieves both built-in categories (like Database Maintenance, Log Shipping) and custom categories created by DBAs.
Get-DbaAgentJobHistory View Source Klaas Vandenberghe (@PowerDbaKlaas) , Simone Bizzotto (@niphold) Windows, Linux, macOS Synopsis Retrieves SQL Server Agent job execution history from msdb database for troubleshooting and compliance reporting.
Description Get-DbaAgentJobHistory queries the msdb database to retrieve detailed execution records for SQL Server Agent jobs, helping you troubleshoot failures, monitor performance trends, and generate compliance reports. This function accesses the same historical data you’d find in SQL Server Management Studio’s Job Activity Monitor, but with powerful filtering and output options.
Rob Sewell (sqldbawithabeard.com) | Simone Bizzotto (@niphlod)
Get-DbaAgentJobOutputFile View Source Rob Sewell (sqldbawithabeard.com) , Simone Bizzotto (@niphlod) Windows, Linux, macOS Synopsis Retrieves output file paths configured for SQL Agent job steps
Description This function returns the file paths where SQL Agent job steps write their output logs. When troubleshooting failed jobs or reviewing execution history, DBAs often need to locate these output files to examine detailed error messages and execution details. The function returns both the local file path and the UNC path for remote access, but only displays job steps that have an output file configured.
Get-DbaAgentJobStep View Source Klaas Vandenberghe (@PowerDbaKlaas), powerdba.eu Windows, Linux, macOS Synopsis Retrieves detailed SQL Agent job step information including execution status and configuration from SQL Server instances.
Description Collects comprehensive details about SQL Agent job steps across one or more SQL Server instances. Returns information about each step’s subsystem type, last execution date, outcome, and current state, which is essential for monitoring job performance and troubleshooting failed automation tasks. You can filter results by specific jobs, exclude disabled jobs, or process job objects from Get-DbaAgentJob to focus on particular maintenance routines or scheduled processes.
Get-DbaAgentLog View Source Chrissy LeMaire (@cl), netnerds.net Windows, Linux, macOS Synopsis Retrieves SQL Server Agent error log entries for troubleshooting and monitoring
Description Retrieves SQL Server Agent error log entries from the target instance, providing detailed information about agent service activity, job failures, and system events. This function accesses the agent’s historical error logs (numbered 0-9, where 0 is the current log) so you don’t have to manually navigate through SQL Server Management Studio or query system views.
Get-DbaAgentOperator View Source Klaas Vandenberghe (@PowerDBAKlaas) Windows, Linux, macOS Synopsis Retrieves SQL Server Agent operators with their notification settings and related jobs and alerts.
Description Retrieves detailed information about SQL Server Agent operators, including email addresses, enabled status, and relationships to jobs and alerts that notify them. Essential for auditing notification configurations, troubleshooting alert delivery issues, and maintaining disaster recovery contact lists. Shows which jobs notify each operator and tracks the last time each operator received email notifications, helping DBAs verify their monitoring and alerting infrastructure is properly configured.
Get-DbaAgentProxy View Source Chrissy LeMaire (@cl), netnerds.net Windows, Linux, macOS Synopsis Retrieves SQL Server Agent proxy accounts and their associated credentials from target instances.
Description Retrieves SQL Server Agent proxy accounts which allow job steps to execute under different security contexts than the SQL Agent service account.
This function is essential for security auditing, compliance reporting, and troubleshooting job step execution permissions.
Returns detailed information including proxy names, associated credentials, descriptions, and enabled status across multiple SQL Server instances.
Get-DbaAgentSchedule View Source Chris McKeown (@devopsfu), devopsfu.com Windows, Linux, macOS Synopsis Retrieves SQL Agent shared schedules with detailed timing and recurrence information.
Description Retrieves all shared schedules from SQL Server Agent along with human-readable descriptions of their timing patterns. These shared schedules can be reused across multiple jobs to standardize maintenance windows and reduce schedule management overhead. The function provides filtering options by schedule name, unique identifier, or numeric ID, making it useful for schedule auditing, documentation, and troubleshooting automated job execution patterns.
Get-DbaAgentServer View Source Claudio Silva (@claudioessilva), claudioessilva.eu Windows, Linux, macOS Synopsis Retrieves SQL Server Agent service configuration and status information
Description Returns detailed SQL Server Agent configuration including service state, logging levels, job history settings, and service accounts. This is essential for auditing Agent configurations across multiple instances, troubleshooting job failures, and documenting environment settings for compliance or migration planning. The function provides a standardized view of Agent properties that would otherwise require connecting to each instance individually through SSMS.
Stephen Bennett, sqlnotesfromtheunderground.wordpress.com
Get-DbaRunningJob View Source Stephen Bennett, sqlnotesfromtheunderground.wordpress.com Windows, Linux, macOS Synopsis Retrieves SQL Server Agent jobs that are currently executing
Description This function returns SQL Server Agent jobs that are actively running at the moment you call it, filtering out any jobs in idle state.
Use this to monitor job execution during maintenance windows, troubleshoot performance issues by identifying resource-consuming jobs, or verify that no jobs are running before performing maintenance operations.