| Author | Garry Bargsley (@gbargsley), blog.garrybargsley.com |
| Availability | Windows, Linux, macOS |
Want to see the source code for this command? Check out Disable-DbaTraceFlag on GitHub.
Want to see the Bill Of Health for this command? Check out Disable-DbaTraceFlag.
Disable a Global Trace Flag that is currently running
The function will disable a Trace Flag that is currently running globally on the SQL Server instance(s) listed.
These are not persisted after a restart, use Set-DbaStartupParameter to set them to persist after restarts.
Disable-DbaTraceFlag
[-SqlInstance] <DbaInstanceParameter[]>
[[-SqlCredential] <PSCredential>]
[-TraceFlag] <Int32[]>
[-EnableException]
[<CommonParameters>]
PS C:\> Disable-DbaTraceFlag -SqlInstance sql2016 -TraceFlag 3226
Disable the globally running trace flag 3226 on SQL Server instance sql2016
The target SQL Server instance or instances.
| Alias | |
| Required | True |
| Pipeline | true (ByValue) |
| Default Value |
Trace flag number to enable globally
| Alias | |
| Required | True |
| Pipeline | false |
| 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 |
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 |