Test-DbaManagementObject

Synopsis

Verifies if specific SQL Server Management Objects (SMO) library versions are installed on target computers.

Description

Checks the Global Assembly Cache (GAC) for Microsoft.SqlServer.Smo assemblies of specified versions. This function helps DBAs ensure the required SMO libraries are available before executing scripts that depend on specific SQL Server client tool versions. Returns detailed results showing which versions exist on each target computer, preventing runtime errors when SMO-dependent automation runs against systems with missing or incompatible client libraries.

Syntax

Test-DbaManagementObject
    [[-ComputerName] <DbaInstanceParameter[]>]
    [[-Credential] <PSCredential>]
    [-VersionNumber] <Int32[]>
    [-EnableException]
    [<CommonParameters>]

Examples

Example: 1

PS C:\> Test-DbaManagementObject -VersionNumber 13

Returns True if the version exists, if it does not exist it will return False

Required Parameters

-VersionNumber

Specifies the major version number(s) of SQL Server SMO assemblies to verify in the Global Assembly Cache.
Common values include 11 (SQL 2012), 12 (SQL 2014), 13 (SQL 2016), 14 (SQL 2017), 15 (SQL 2019), and 16 (SQL 2022).

Optional Parameters

-ComputerName

Specifies the target computer(s) to check for SMO assemblies. Accepts pipeline input and defaults to the local computer.
Use this when verifying SMO library versions across multiple servers in your environment.

-Credential

This command uses Windows credentials. This parameter allows you to connect remotely as a different user.

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