Pre-staging a SQL Server patch package

  1. From the Management Console main page, select Patching > Patch Repository in the Context Frame.
  2. On the Patch Repository page, select a patch package and select Pre-Stage from the list box for that row.
  3. On the MS SQL Server Pre Stage Patch Media page, populate the following fields, and click Next.

    Patch Candidate Field


    Remote Account Information

    Type a valid domain administrator account domain, user name, and password in the Remote Account Domain, Remote Account Username, and Remote Account Password fields, respectively.

    Note: This field is enabled only if you select a SQL Server Instance on a WSFC node. If you are patching standalone SQL Server Instances on non-clustered nodes, BDA does not prompt you for credentials to a domain administrator account.   

    Force Availability Group Failover(Displays only if you have the SQL Server Availability Group Force capability and the Instances section contains instances on an Availability Group) Select this option to allow a SQL Server Availability Group to fail over with data loss.
    Selecting this option enables you to select all the instances participating in an Availability Group to fail over with data loss, even if all the databases are not synchronized.


    Displays the default BDA template selected from the Default Template field in the Edit Existing Package wizard. Optionally, you can select a template for this operation. See Managing templates for SQL Server. If you select a template, you can click Skip Ahead to advance directly to the next step that requires input. An information message appears in the step, in green type, listing the fields that require entries before advancing to the next step.

    (Applicable for version 8.9.01 and later) Use /ALLINSTANCES

    Select this check box to use the ALLINSTANCES parameter when running the SQL Server patch installer to apply/rollback the patch to all applicable instances of SQL Server on a given node rather than apply/rollback a patch to each instance individually. For more information about this parameter, see

    Important: It is required to have more than one candidate instance for a given node and you must select all the candidate instances on that node for BDA to use ALLINSTANCES to apply a patch to the instances on a node. BDA will not proceed unless this option is disabled. The pre and post patching scripts in this patch package still run individually for each instance at the appropriate time. This option is available only to users having the "SQL Server Patch with /ALLINSTANCES" capability, see Capabilities tables 1.

    Note: During the process of patching a Clustered SQL Server Instance using ALLINSTANCES parameter, active instances are failed over in the middle and at the end of patching. After the patching has been done BDA restores these instances that were active when patching started.


    Select the instances where you want to copy and extract this patch package. The candidates for this patch package are determined by the patch version number defined when you created patch package.

    Note: The candidates list does not get refreshed automatically. Click the Reload Candidates button to refresh the list.

  4. If the Custom Fields page appears, update the custom fields as necessary, and click Next.
    This page appears only when in the BMC Database Automation XML template, either custom fields are defined used for this activity or NEW IN 8.9.03any custom fields are defined for the scheduling options (present on the Scheduling page in this wizard). If you have defined custom fields, value of those options on the Scheduling page will be derived from these custom fields. For more information, see Adding custom fields to a template.

  5. In the Job Options page, specify any of the following Job options, and click Next.




    Notification Emails

    Email List

    (Optional) Click Add Email to add email addresses to the notification list.

    Job Administration

    Cleanup Agent Logs

    (Optional) Select to automatically remove logs that are generated by BMC Database Automation on the Agent after the job is complete.

  6. In the Scheduling page, select when to run this job in the Job Execution field, and click Next.
    NEW IN 8.9.03If you choose to run the job now or at a future time, optionally, you can use the Set Maintenance Window option to specify the Maintenance Window Start Time and the Maintenance Window End Time during which the job should be scheduled and running.
  7. In the Summary page, review the information.
    To make changes, do the following:
    1. Click Go to to return to the provisioning step that you want to edit.
    2. Make your changes.
    3. Click Save and Review to return to the Summary page.
  8. Specify your verification preferences.
    • To continue with database creation after the pre-verification tests have been successfully run without manual intervention, select Automatically Continue If All Tests Succeed.
    • To create the database without having first run the pre-verification steps, select Skip Pre-Verification Tests.


      The Skip Pre-Verification Tests option should only be used when you are certain all tests can succeed. The option skips verification and advances directly to the actual provisioning activity.

  9. Click Execute Job or Schedule Job (depending on your selection in the Scheduling page).
Was this page helpful? Yes No Submitting... Thank you