Author Klaas Vandenberghe (@powerdbaklaas)
Availability Windows, Linux, macOS


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


Gets SQL Instance user options of one or more instance(s) of SQL Server.


The Get-DbaInstanceUserOption command gets SQL Instance user options from the SMO object sqlserver.


    [-SqlInstance] <DbaInstanceParameter[]>
    [[-SqlCredential] <PSCredential>]




Example: 1
PS C:\> Get-DbaInstanceUserOption -SqlInstance localhost

Returns SQL Instance user options on the local default SQL Server instance

Example: 2
PS C:\> Get-DbaInstanceUserOption -SqlInstance sql2, sql4\sqlexpress

Returns SQL Instance user options on default instance on sql2 and sqlexpress instance on sql4

Example: 3
PS C:\> 'sql2','sql4' | Get-DbaInstanceUserOption

Returns SQL Instance user options on sql2 and sql4

Required Parameters


The target SQL Server instance or instances. This can be a collection and receive pipeline input to allow the function to be executed against multiple SQL Server instances.

Required True
Pipeline true (ByValue)
Default Value

Optional Parameters


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.

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.

Required False
Pipeline false
Default Value False