Stop-DbaTrace

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

Synopsis

Stops SQL Server traces

Description

Stops SQL Server traces

Syntax

Stop-DbaTrace
    [[-SqlInstance] <DbaInstanceParameter[]>]
    [[-SqlCredential] <PSCredential>]
    [[-Id] <Int32[]>]
    [[-InputObject] <Object[]>]
    [-EnableException]
    [-WhatIf]
    [-Confirm]
    [<CommonParameters>]

Examples

Example: 1

PS C:\> Stop-DbaTrace -SqlInstance sql2008

Stops all traces on sql2008

Example: 2

PS C:\> Stop-DbaTrace -SqlInstance sql2008 -Id 1

Stops all trace with ID 1 on sql2008

Example: 3

PS C:\> Get-DbaTrace -SqlInstance sql2008 | Out-GridView -PassThru | Stop-DbaTrace

Stops selected traces on sql2008

Optional Parameters

-SqlInstance

The target SQL Server instance

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

-Id

A list of trace ids

-InputObject

Internal parameter for piping

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