The basis of SPADE is in its config file

The config file has five (5) major sections

AppSettings

This section contains key/value pairs for Global Options.

ScriptConfigs

The ScriptConfigs section is used as a central location for any pre/post install scripts that require end user configuration. The Name attribute for each Script element reflects the name of the Script that it applies to and there is a separate Param element for each configurable parameter. Most of the values are blank and will need to be populated for your environment. If any of the values are left blank, then the corresponding script will be skipped when the tool is used.

DataCenters

The DataCenters section is used to support environments that are spread across multiple data centers. Because the SPADE process will copy over the installation files for the version of SQL Server that is specified, sometimes 6GB or more, this node was created to allow the user to specify a separate file location that is local to each data center. Only one entry is required and must point to the folder location that will house the SPADE files.

Environments

The DataCenters section is used to support environments that are spread across multiple data centers. Because the SPADE process will copy over the installation files for the version of SQL Server that is specified, sometimes 6GB or more, this node was created to allow the user to specify a separate file location that is local to each data center. Only one entry is required and must point to the folder location that will house the SPADE files.

SqlVersions

The SqlVersions section is the heart of the configuration file and allows you to specify each version/edition of SQL Server that you choose to support and what its standard configuration looks like. Each Version element contains the following information:

1) Version Name – the name of the SQL Server version

2) ConfigurationTemplate – the template used to create the unattended install file - these files are required for the SPADE process and should not be modified

3) ProductStrings – a named list of product strings that are used to define the standard features of each install - this list can be modified and added to, but should always have a default string defined

4) Editions – a list of the different editions of SQL Server that you want SPADE to be able to install – each entry defines the edition name, the license key, and the sub folder that will contain files from the installation media

NOTE: SQL 2005 keys should be entered without dashes (-) and SQL 2008 and above should be entered with dashes

5) TemplateOverries – this list defines unattended install options that are used to apply your organizations configurations for a standard SQL Server setup

NOTE: for a full list of the possible settings, please review the Books Online documentation for installing SQL Server from the command line - http://msdn.microsoft.com/en-us/library/ms144259.aspx

Last edited Aug 23, 2016 at 9:03 PM by JasonCarter80, version 1

Comments

No comments yet.