Author Chrissy LeMaire (@cl),
Availability Windows, Linux, macOS


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


Returns a bunch of information from dm_exec_connections.


Returns a bunch of information from dm_exec_connections which, according to Microsoft:
"Returns information about the connections established to this instance of SQL Server and the details of each connection. Returns server wide connection information for SQL Server. Returns current database connection information for SQL Database."


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




Example: 1
PS C:\> Get-DbaConnection -SqlInstance sql2016, sql2017

Returns client connection information from sql2016 and sql2017

Required Parameters


The target SQL Server instance or instances. Server(s) must be SQL Server 2005 or higher.

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.

Alias Credential,Cred
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