Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

How to deploy SQL Server 2008

This topic was edited by a BMC Contributor and has not been approved.  More information.

Contributor content

This topic was created by a BMC Contributor and has not been approved. More information.

 This page describes how to deploy SQL Server 2008 using BMC Server Automation. For information on deploying to a clustered environment, see How to deploy SQL Server 2008 R2 Cluster.

Silent installation information for SQL Server 2008 R2 NON-Cluster

Parameter/INI file changes/additions necessary for unattended deployments:

  1. Set QUIET="True"
  2. Comment out UIMODE (place a semi-colon in front of it)
  3. Comment out ADDCURRENTUSERASSQLADMIN (place a semi-colon in front of it)


psexec is not required to call the "setup.exe" command via BladeLogic, as long as system accounts are selected for the various SQL service startup accounts. However, if named accounts are used, the SQL install will fail attempting to add the password values to the XML file it creates for unattended responses during the install process. Utilize the '-u' & '-p' options to provide domain account credentials for psexec to use. The '-h' option may also be necessary to have psexec execute the command with elevated privileges. If named accounts are used, the following parameter/INI file additions are necessary:


Another set of instructions:

blcli_storeenv ENC_PWD
blcli_execute Property decryptPropertyValue $ENC_PWD

Silently installing SQL Server 2008

How to perform a silent unattended install of SQL Server 2008 R2 (Standard or Enterprise) using a configuration file.

With the instructions below, you’ll be able to create a new customized SQL silent installation in minimal time. Note that the configuration below does not work with the Express edition of SQL Server 2008 R2.

  1. Run setup.exe.
  2. Click the Installation tab
  3. Click New Installation.
  4. Go through the wizard. Enter product key, accept license, install setup support files, and select the features that you want to install:
  5. Continue the installation until you reach the Ready To Install step. Notice the path to the configuration file highlighted below in blue.
  6. Now that you have the configuration file, copy it to your own folder or network share where you want to start the unattended installation.
  7. Cancel setup since we’re interested in the unattended silent mode of installation; not the UI one.
  8. Edit the configuration file as follows:
    • Set QUIET to “True”. This specifies that Setup will run in a quiet mode without any user interface (i.e. unattended installation).
    • Set SQLSYSADMINACCOUNTS to “BUILTIN\ADMINISTRATORS”. This will ensure that administrators on the machine are added as members of the sysadmin role. You can set its value based on your needs (Ex: SQLSYSADMINACCOUNTS=”domain\YourUser”), but this is the more generic approach.
    • Add PID and set its value to your product license key. If your setup.exe already comes preloaded with the key, there is no need to add this option to the configuration file.
    • Add IACCEPTSQLSERVERLICENSETERMS and set its value to “True”. This is to required to acknowledge acceptance of the license terms when the /Q (that is, QUIET) parameter is specified for unattended installations.
      • Remove the ADDCURRENTUSERASSQLADMIN parameter. The reason is that this parameter can’t be used when SQLSYSADMINACCOUNTS is specified, and it only applies to Express installations.
      • Remove the UIMODE parameter as it can’t be used with the QUITE parameter.
      • Remove INSTALLSHAREDDIR, INSTALLSHAREDWOWDIR, INSTANCEDIR parameters since we want to install on the default installation directories.
      • If you want to change the features that this setup will install, there is no need to go with the full steps again. You can simply change the value for the FEATURES parameter. For example, the features I selected (shown in first screenshot above) will generate FEATURES=SQLENGINE,SSMS,ADV_SSMS in the configuration file.  You can change that based on your needs. The full list of available feature parameters and their descriptions is located here.
  9. After getting the configuration file ready, you’ll need to run setup.exe passing the configuration file as a parameter.
    "<path to SQL setup folder>\setup.exe"/ConfigurationFile="<path to config file>"

Sample ConfigurationFile.ini

Download: [ConfigurationFile.ini|]


Next, use the relevant silent installation parameters (depending on the version you are deploying) when creating a Software package in the Depot.

SQL Server 2008/2012 Native Client


msiexec /x "??SOURCE??" /qn

SQL Server 2008 R2 Service Pack 1 Silent Install

"??SOURCE??" /quiet /allinstances /IAcceptSQLServerLicenseTerms

SQL Server 2008 R2 Cumulative Update 5

"??SOURCE??" /quiet /action=patch /allinstances /IAcceptSQLServerLicenseTerms

SQL Server 2008 R2 Management Studio

"??SOURCE"/setup.exe /Q /ACTION=INSTALL /FEATURES=Tools /IAcceptSQLServerLicenseTerms

Create a Deploy Job, and test deploying your SQL Server Software Package against one or more test servers.

Was this page helpful? Yes No Submitting... Thank you