Invoke-DbaCycleErrorLog

Synopsis

Cycles the current SQL Server error log and/or SQL Agent error log to start fresh log files

Description

Archives the current error log files and creates new ones for SQL Server instance and/or SQL Agent. This operation is typically performed during maintenance windows to manage log file sizes and establish clean baselines for troubleshooting. When cycled, the current error log becomes the archived log (errorlog.1) and a new error log starts capturing events.

Syntax

Invoke-DbaCycleErrorLog
    [-SqlInstance] <DbaInstanceParameter[]>
    [[-SqlCredential] <PSCredential>]
    [[-Type] <String>]
    [-EnableException]
    [-WhatIf]
    [-Confirm]
    [<CommonParameters>]

Examples

Example: 1

PS C:\> Invoke-DbaCycleLog -SqlInstance sql2016 -Type agent

Cycles the current error log for the SQL Server Agent on SQL Server instance sql2016

Example: 2

PS C:\> Invoke-DbaCycleLog -SqlInstance sql2016 -Type instance

Cycles the current error log for the SQL Server instance on SQL Server instance sql2016

Example: 3

PS C:\> Invoke-DbaCycleLog -SqlInstance sql2016

Cycles the current error log for both SQL Server instance and SQL Server Agent on SQL Server instance sql2016

Required Parameters

-SqlInstance

The target SQL Server instance or instances.You must have sysadmin access and server version must be SQL Server version 2000 or higher.

Optional Parameters

-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.

-Type

Specifies which error log to cycle: ‘instance’ for SQL Server instance log, ‘agent’ for SQL Agent log.
When omitted, cycles both logs simultaneously which is the typical maintenance approach.
Use specific values when you need to manage log sizes independently or troubleshoot specific services.

-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.

-WhatIf

If this switch is enabled, no actions are performed but informational messages will be displayed that explain what would happen if the command were to run.

-Confirm

If this switch is enabled, you will be prompted for confirmation before executing any operations that change state.