|Author||Garry Bargsley (@gbargsley), http://blog.garrybargsley.com|
|Availability||Windows, Linux, macOS|
Locate a SQL Server that has generated any memory dump files.
The type of dump included in the search include minidump, all-thread dump, or a full dump. The files have an extendion of .mdmp.
Get-DbaDump [-SqlInstance] <DbaInstanceParameter> [[-SqlCredential] <PSCredential>] [-EnableException] [<CommonParameters>]
PS C:\> Get-DbaDump -SqlInstance sql2016
Shows the detailed information for memory dump(s) located on sql2016 instance
PS C:\> Get-DbaDump -SqlInstance sql2016 -SqlCredential sqladmin
Shows the detailed information for memory dump(s) located on sql2016 instance. Logs into the SQL Server using the SQL login 'sqladmin'
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.
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.
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.