Patching All Instances Of SQL On One System With Shavlik Protect

Version 3

    Purpose  

     

    This document is meant to provide information about how to patch all instances of SQL on one system with Shavlik Protect.

     

    Microsoft allows multiple instances of SQL database engine to run side-by-side on a single system. This can lead to some odd behavior when patching, but in this document we will try to cover the best practice for applying patches to all instances and what to do if it seems there is any problem with detection of multiple SQL instances.

     

    Description

     

    Best Practice for Deploying patches to all instances

     

    For any given patch that affects Microsoft SQL Server, Shavlik Protect's detection will check all applicable files and registry keys for each instance of SQL that exists on the system. Note: The database engine services must be installed for an actual SQL instance to exist. Shavlik Protect will not detect or apply patches if the database engine services are not installed.

     

    Based on this, the best practice is very simple. You should be able to patch all instances by peforming a Security Patch Scan or WUscan with Shavlik Protect, and then deploy all missing patches. This method is not using the /allinstances switch that Microsoft enables for SQL patches. This just means that Shavlik Protect is detecting each patch individually for every instance of SQL that exists on the target system(s).

     

    Actions to take if all instances of SQL are not being patched

     

    If a SQL patch was not applied to a certain instance on the initial deployment of all patches, you may need to do the following:

    • Ensure that you are using the latest patch definitions. You can check this under Help > About. Help > Refresh Files will update definitions.
    • If you know that you already attempted installation of the patch - try manually running the patch file on the target system. Does it error out?
    • If this patch was not displayed missing previously - you can deploy again. This may be all it takes to resolve this.
    • If patches are repeatedly shown missing or you believe there may be a detection issue it will be best to contact support and provide the following:
      • Full description of the current problem taking place
      • Logs from a scan of a single system that has the issue.
      • Any screenshots that you believe will be helpful
      • DPD Trace

     

    Additional Information

     

    The following resources may be helpful in learning more about patching SQL instances:

     

    Affected Product(s)

     

    Shavlik Protect 9.x