Creating a SQL Server patch package

This topic describes the procedure to create a SQL Server patch package.

Before you begin

Download the patches that you want to apply. The patch file must be a ZIP file (.zip) or an executable (.exe).

To create an SQL Server patch package

1. From the Management Console main page, in the Context Frame, select Patching > Patch Repository.
2. On the Patch Repository tab, click Create New Package.

3. On the Package Configuration page, fill the following fields, and click Next.

   Patch Field	Description
   Database Type	Select the type of database for this patch package.
   Patch File	Click Browse to locate the patch file that you want to include in this patch package.

4. On the Package Settings page, fill the following fields, and click Next.

   Patch Field	Description
   Package Name	Type a unique name for this patch package. This field cannot be edited after patch package creation.
   Description	Type a description of the patch package.
   Default Template	(Optional) Select a default template for the patch package.
   Container	Assign the patch package to a domain. Note The domain selected as the Container determines which users can modify the patch package. Users with Action run, edit, delete or export capabilities for the Container domain can perform all tasks against the patch package, whereas users with capabilities in the Available To domains can only use the patch package.
   Available To	(Optional) Select additional domains to which this patch package is available for use.
   Selected Available Domains	Lists the domains in which this patch package is available to authorized users.

5. On the Package Attributes page, fill the following fields, and click Next.

   Patch Field	Description
   MS Patch ID	Type the version number that the SQL Server has after the installation of this patch. For example, 9.0.3047. The patch version number entered here is used to determine which SQL Server instances are candidates for this patch.
   MS Patch Level	Enter the patch level of the patch.
   Set as Standard	(Optional) Select to identify this patch package as standard, and have BMC Database Automation display targets that require remediation. The Patch Standard tab displays the patch packages marked as standard, enabling you to easily track, report, and fix databases that are out of compliance with your organizational standards. See also Managing standard patch packages.
   Can Rollback	(Optional) Select to allow the patch package to be rolled back after it is applied. If Microsoft provides the capability to rollback this patch package (in general, hotfixes can be rolled back and service packs cannot, but read the readme file for the patch to determine whether it is capable of roll back), then selecting this option enables the roll back function for this patch.
   Specify Command Line Options	(Optional) Select to enable Command Line Options to be passed to the patch installer when applying the SQL Server patch.
   Command Line Options	(Optional) Enter commands to be passed to the patch installer when the SQL Server patch package is applied. Click Add Option to add CLI options.  Note Template variables work almost the same as they do for Sybase, with the following exceptions: Instead of {GA_PATCH_DIR}/setup.bin, the value at the beginning of the command line must be setup.exe. Instead of enclosing the command line options in single quotes, the values must be enclosed in double quotes.
   Command Line	(Optional) Click Populate Command Line to display the command line that is used to apply this patch package in the CLI.

6. On the Package Targets page, enter the values by moving the wanted items to the Selected box for each field, and click Next.

   Patch Field	Description
   Target Operating Systems	Define the valid OS list that are considered legitimate candidates for this patch package.
   Target Architectures	Define the list of valid processor types (architectures) that are considered legitimate candidates for this patch package. The target architecture must match the software it is patching.
   Target Applications	Define the versions of applications (for example, Oracle or Microsoft SQL Server) that are considered legitimate candidates for this patch package.

   Note

   To add to the list of available choices for the Target Operating Systems and Target Applications fields, see Adding target OS and applications to a patch package.

7. On the Package Scripts page, fill the following fields, and click Next.

   Section	Field	Description
   Install Scripts	Pre-Install Shutdown	(Optional) Specifies the location of the install script to be run before the application shutdown is initiated.
   	Pre-Install	(Optional) Specifies the location of the install script to be run before the installation of the patch package.
   	Post-Install	(Optional) Specifies the location of the install script to be run after the installation of the patch package.
   	Post-Install Startup	(Optional) Specifies the location of the install script to be run after the application startup is initiated.
   Rollback Scripts	Pre-Rollback Shutdown	(Optional) Specifies the location of the rollback script to be run before the application shutdown is initiated.
   	Pre-Rollback	(Optional) Specifies the location of the rollback script to be run before the rollback of the patch package.
   	Post-Rollback	(Optional) Specifies the location of the rollback script to be run after the rollback of the patch package.
   	Post-Rollback Startup	(Optional) Specifies the location of the rollback script to be run after the application startup is initiated.

8. On the Package Additional Files page, specify any additional files as follows, and click Next.
   Additional files can be added to a patch package. They can be added one at a time or as a prepackaged .zip file.

   Patch Field	Description
   Additional Files	Click Add File to add files, one at a time, for inclusion in this patch package.
   Additional Zip File	Click Browse to locate and upload a .zip file containing files for inclusion in this patch package.

9. On 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.
10. Click Create Package.