sqlspade Wiki Rss Feed

Updated Wiki: Configuring SQL Scripted PowerShell Automated Deployment Engine (SPADE)

Sarasotasql — Mon, 02 Jan 2012 19:21:28 GMT

1) Download the latest release from http://sqlspade.codeplex.com

2) Right-click the zip file, click Properties and select Unblock – this step is important because blocked PowerShell scripts cannot be executed if your ExecutionPolicy setting is RemoteSigned or higher.

3) Unzip the file (preferably to a network share)

4) Edit the Run-Install.config file for your configuration

AppSettings Section

<!-- This section contains default settings to be used for all installs - these can be overridden
-->

<AppSettings>

  <Setting
Name="WindowsScriptsFolder"
Value="C:\Windows\Script"/>

  <Setting
Name="FilePath"
Value="S:\Tools"/>

</AppSettings>

The AppSettings section contains basic configuration options that apply to the process, and are not a specific version of SQL.

1) WindowsScriptsFolder – this setting defines the folder on the destination server that hold any scripts located in the PowerShellScripts folder

2) FilePath – defines the default working folder used to copy all of the setup files to the destination server

ScriptConfigs Section

<!-- This section contains settings used by individual pre/post scripts - these must be reviewed and set
-->

<ScriptConfigs>

  <Script
Name="Verify-AdminGroup">

    <Param
Name="Domain"
Value="" />

    <Param
Name="Group"
Value="" />

  </Script>

  <Script
Name="Verify-Drives">

    <Param
Name="FailOnFileSystem"
Value="1" />

    <Param
Name="FailOnDiskAlign"
Value="1" />

    <Param
Name="FailOnCompressed"
Value="1" />

  </Script>

  <Script
Name="Check-AncillaryServices">

    <Param
Name="Services"
Value="" />

  </Script>

  <Script
Name="Verify-MgmtServerAccess">

    <Param
Name="Servers"
Value="" />

  </Script>

  <Script
Name="Resize-TempDB">

    <Param
Name="MaxFileCount"
Value="8" />

    <Param
Name="MaxFileInitialSizeMB"
Value="1024" />

    <Param
Name="MaxFileGrowthSizeMB"
Value="2048" />

    <Param
Name="FileGrowthMB"
Value="512" />

    <Param
Name="CoreMultiplier"
Value="1" />

  </Script>

  <Script
Name="Add-CMSRegistration">

    <Param
Name="CMSServer"
Value="" />

    <Param
Name="CMSInstance"
Value="" />

    <Param
Name="CMSGroupName"
Value="" />

  </Script>

  <Script
Name="Get-PortNumber">

    <Param
Name="PortNumber"
Value="1433" />

  </Script>

  <Script
Name="Configure-DatabaseMail">

    <Param
Name="Email"
Value="" />

    <Param
Name="Relay"
Value="" />

    <Param
Name="ReplyTo"
Value="" />

    <Param
Name="DisplayName"
Value="" />

    <Param
Name="ProfileName"
Value="" />

  </Script>

</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.

*Note – in the Configure-DatabaseMail section you can substitute “[computername]” in any of the Value parameters and it will be replaced at runtime with the name of the server you are installing on. This can be used if you want to include the server name in the email address to see what server an error originated on .

DataCenters Section

<DataCenters>

  <!-- This section contains the list of valid data centers and their respective Auto-Install source locations-->

  <DataCenter
Name="Data Center 1"
Location="Location 1"
FilePath="\\alfkidc-2\DataCenter1\AutoInstall\\cf0 " />

  <DataCenter
Name="Data Center 2"
Location="Location 2"
FilePath="\\alfkidc-2\DataCenter2\AutoInstall\\cf0 " />

</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.

SqlVersions Section

<Version
Name="SQL2008">

  <ConfigurationTemplate
Name="Configuration_2008.ini"
Category="SQLSERVER2008" />

  <ProductStrings>

    <ProductString
Name="Default"
Value="SQLENGINE,REPLICATION,FULLTEXT,CONN,BC,SSMS,ADV_SSMS" />

    <ProductString
Name="DefaultPlusIS"
Value="SQLENGINE,REPLICATION,FULLTEXT,BIDS,CONN,IS,BC,SSMS,ADV_SSMS" />

    <ProductString
Name="Minimal"
Value="SQLENGINE,CONN,BC,SSMS,ADV_SSMS" />

    <ProductString
Name="Full"
Value="" />

  </ProductStrings>

  <Editions>

    <Edition
Name="Standard"
Key=""
FolderName="SQL2008\Standard" />

    <Edition
Name="Enterprise"
Key=""
FolderName="SQL2008\Enterprise" />

  </Editions>

  <TemplateOverrides>

    <Setting
Name="SQLSYSADMINACCOUNTS"
Value='"alfki\SQL_DBA" "alfki\SQL_Ops"' />

    <Setting
Name="INSTALLSQLDATADIR"
Value="C:\SystemDbs" />

    <Setting
Name="SQLBACKUPDIR"
Value="C:\Backups" />

    <Setting
Name="SQLUSERDBDIR"
Value="C:\Data" />

    <Setting
Name="SQLUSERDBLOGDIR"
Value="C:\Logs" />

  </TemplateOverrides>

</Version>

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

5) Run the SQL SPADE Helper application to build the SQL Server installation folders - Launch the SqlSpadeHelper.exe application located in the Tools folder where you unzipped SPADE

Click on the “SPADE Folder Builder” button

Click on the “…” button and browse to the Run-Install.config file

Select the Data Center that you want to build the folder structure for and then click the Check button

For each entry that is missing or empty, select the row and select the operation to perform

1) None – take no action

2) Create Folder – create the folder, but leave it empty

3) Populate Folder – create and populate the folder from the media source

Click on the Build Folders button

7) Review the scripts in the PreScripts and PostScripts folders to ensure that they meet your needs. Any script that you choose to not use can either be deleted or excluded from the Auto-Install process by putting an “_” at the beginning of the file name.

Updated Wiki: Home

sarasotasql — Mon, 10 Oct 2011 03:25:43 GMT

Project Description
SPADE simplifies the process of standing up a new SQL Server instance by applying standard Operating System pre-configurations, Installing SQL Server and then applying post-configurations and creating standard objects.

SPADE is a tool that is designed to speed up your standard deploymets of SQL Server. You may be saying "But I can already do an unsattended install"...but that's not all that's involved in most server builds. There are Operating System configurations like Microsoft Distrubuted Transaction Coordinator (MSDTC), Local Security Policy and others. I'm sure that you also have standard SQL objects that need to be deployed like Stored Procedures, Agent Jobs, Operators, etc. All of this can be done by SPADE automatically by running 1 simple PowerShell script.

Every organization is different, so this tool has been built so that it can easily be customized without requiring you to be a master of PowerShell. A simple XML configuration file defines the options for your standard build. For those non-standard, or "one-off" builds, the script has been defined so that you can change things for a single build without having to change the configuration file.

The current release supports standalone installs of SQL 2005, 2008, 2008R2, and "Denali".

Imagine being able to stand up AND completely configure a new SQL Instance in under 20 minutes. If that sounds appealing to you, then download SPADE and give it a try.

Updated Wiki: Temporary Post Used For Theme Detection (8342f579-f120-41c6-9fdc-40be8dc784b0 - 3bfe001a-32de-4114-a6b4-4005b770f6d7)

Sarasotasql — Sun, 25 Sep 2011 13:25:58 GMT

This is a temporary post that was not deleted. Please delete this manually. (03f0e129-99ca-4d46-81a0-de330a21d992 - 3bfe001a-32de-4114-a6b4-4005b770f6d7)

Updated Wiki: Documentation

sarasotasql — Sun, 25 Sep 2011 13:22:41 GMT

Configuring SQL Scripted PowerShell Automated Deployment Engine (SPADE)

Running SQL Scripted PowerShell Automated Deployment Engine (SPADE)

Updated Wiki: Running SQL Scripted PowerShell Automated Deployment Engine (SPADE)

sarasotasql — Sun, 25 Sep 2011 13:22:22 GMT

For instructions on how to setup and configure SPADE please see the following post :

To run SQL SPADE:

1) Log onto the server you need to install on

2) Create a working folder on a drive that is large enough to hold the installation files for the version of SQL you are going to install

3) Copy the following files from the path where you configured SAPDE to your working folder:

- Start.bat

- Start-SqlSpade.ps1

- Run-Install.ps1

- Run-Install.config

4) Double click the Start.bat file to launch PowerShell ISE in administrator mode, accepting the UAC prompt if you receive it

5) In the script file that is opened edit the following lines:

- $ht.Add("SqlVersion", 'Sql2005') –The version of SQL you want to install (i.e. SQL2005, SQL2008, SQL2008R2)

- $ht.Add("SqlEdition", 'Standard') – The edition of SQL you want to install (i.e. Standard, Enterprise, Developer)

- $ht.Add("ServiceAccount", 'alfki\SqlService') – The service account you want SQL to run under

- $ht.Add("ServicePassword", 'P@ssw0rd1') – The password for the service account specified above

- $ht.Add("SysAdminPassword", 'P@ssw0rd1') – The password for the SA account

- $ht.Add("FilePath", 'S:\Tools') – The working folder that you created to perform the install from

- $ht.Add("DataCenter", 'Data Center 1') – The named Data Center that you want to pull the install files from

- #$ht.Add("ProcessorArch", '') – The CPU architecture of the system, uncomment and set the value to ‘x86’ when forcing a 32 bit install

- #$ht.Add("Debug", 'True') – Used for debugging the system by logging additional information

- #$ht.Add("Simulation", 'True') – Used for troubleshooting file copy code by logging that a file copy would have occurred, but does not actually copy the files

- $ht.Add("DbaTeam", 'DBA-SQL') – Used by the 300-Server-Set-DbaTeam.ps1 post install script to set an extended property on the master database

- $ht.Add("InstanceName", 'sqldev1') – The instance name to install as, leave blank for a default instance

- $ht.Add("ProductStringName", 'Default') – The named product string that identifies the components to be installed

Note – you can also override any SQL configuration setting by adding it to the $overrides hashtable – please see http://msdn.microsoft.com/en-us/library/ms144259.aspx for a list of available configuration settings

6) Modify the function call as needed with the following switches

-PreOnly – runs only the Pre Install portion of the process and can be combined with –InstallOnly and –PostOnly

-InstallOnly – runs only the SQL Install portion of the process and can be combined with –PreOnly and –PostOnly

-PostOnly – runs only the Post Install portion of the process and can be combined with –PreOnly and –InstallOnly

-Full – runs the entire process, and is the same as using –PreOnly, –InstallOnly, and –PostOnly combined

-DontCopyLocal – skips the copy of the SQL installation media and runs the install from the network location

-Verbose – Adds additional logging to the console window

-WhatIf – Skips the execution of the SQL Install and Post Install, but logs the setup statement that would have been executed

Updated Wiki: Running SQL Scripted PowerShell Automated Deployment Engine (SPADE)

Sarasotasql — Sun, 25 Sep 2011 13:21:23 GMT

For instructions on how to setup and configure SPADE please see the following post :

To run SQL SPADE:

1) Log onto the server you need to install on

2) Create a working folder on a drive that is large enough to hold the installation files for the version of SQL you are going to install

3) Copy the following files from the path where you configured SAPDE to your working folder:

- Start.bat

- Start-SqlSpade.ps1

- Run-Install.ps1

- Run-Install.config

4) Double click the Start.bat file to launch PowerShell ISE in administrator mode, accepting the UAC prompt if you receive it

5) In the script file that is opened edit the following lines:

- $ht.Add("SqlVersion", 'Sql2005') –The version of SQL you want to install (i.e. SQL2005, SQL2008, SQL2008R2)

- $ht.Add("SqlEdition", 'Standard') – The edition of SQL you want to install (i.e. Standard, Enterprise, Developer)

- $ht.Add("ServiceAccount", 'alfki\SqlService') – The service account you want SQL to run under

- $ht.Add("ServicePassword", 'P@ssw0rd1') – The password for the service account specified above

- $ht.Add("SysAdminPassword", 'P@ssw0rd1') – The password for the SA account

- $ht.Add("FilePath", 'S:\Tools') – The working folder that you created to perform the install from

- $ht.Add("DataCenter", 'Data Center 1') – The named Data Center that you want to pull the install files from

- #$ht.Add("ProcessorArch", '') – The CPU architecture of the system, uncomment and set the value to ‘x86’ when forcing a 32 bit install

- #$ht.Add("Debug", 'True') – Used for debugging the system by logging additional information

- #$ht.Add("Simulation", 'True') – Used for troubleshooting file copy code by logging that a file copy would have occurred, but does not actually copy the files

- $ht.Add("DbaTeam", 'DBA-SQL') – Used by the 300-Server-Set-DbaTeam.ps1 post install script to set an extended property on the master database

- $ht.Add("InstanceName", 'sqldev1') – The instance name to install as, leave blank for a default instance

- $ht.Add("ProductStringName", 'Default') – The named product string that identifies the components to be installed

Note – you can also override any SQL configuration setting by adding it to the $overrides hashtable – please see http://msdn.microsoft.com/en-us/library/ms144259.aspx for a list of available configuration settings

6) Modify the function call as needed with the following switches

-PreOnly – runs only the Pre Install portion of the process and can be combined with –InstallOnly and –PostOnly

-InstallOnly – runs only the SQL Install portion of the process and can be combined with –PreOnly and –PostOnly

-PostOnly – runs only the Post Install portion of the process and can be combined with –PreOnly and –InstallOnly

-Full – runs the entire process, and is the same as using –PreOnly, –InstallOnly, and –PostOnly combined

-DontCopyLocal – skips the copy of the SQL installation media and runs the install from the network location

-Verbose – Adds additional logging to the console window

-WhatIf – Skips the execution of the SQL Install and Post Install, but logs the setup statement that would have been executed

Updated Wiki: Configuring SQL Scripted PowerShell Automated Deployment Engine (SPADE)

Sarasotasql — Sat, 24 Sep 2011 20:53:13 GMT

1) Download the latest release from http://sqlspade.codeplex.com

3) Unzip the file (preferably to a network share)

4) Edit the Run-Install.config file for your configuration

AppSettings Section

<!-- This section contains default settings to be used for all installs - these can be overridden
-->

<AppSettings>

  <Setting
Name="WindowsScriptsFolder"
Value="C:\Windows\Script"/>

  <Setting
Name="FilePath"
Value="S:\Tools"/>

</AppSettings>

The AppSettings section contains basic configuration options that apply to the process, and are not a specific version of SQL.

1) WindowsScriptsFolder – this setting defines the folder on the destination server that hold any scripts located in the PowerShellScripts folder

2) FilePath – defines the default working folder used to copy all of the setup files to the destination server

ScriptConfigs Section

<!-- This section contains settings used by individual pre/post scripts - these must be reviewed and set
-->

<ScriptConfigs>

  <Script
Name="Verify-AdminGroup">

    <Param
Name="Domain"
Value="" />

    <Param
Name="Group"
Value="" />

  </Script>

  <Script
Name="Check-AncillaryServices">

    <Param
Name="Services"
Value="" />

  </Script>

  <Script
Name="Verify-MgmtServerAccess">

    <Param
Name="Servers"
Value="" />

  </Script>

  <Script
Name="Resize-TempDB">

    <Param
Name="MaxFileCount"
Value="8" />

    <Param
Name="MaxFileInitialSizeMB"
Value="1024" />

    <Param
Name="MaxFileGrowthSizeMB"
Value="2048" />

    <Param
Name="FileGrowthMB"
Value="512" />

    <Param
Name="CoreMultiplier"
Value="1" />

  </Script>

  <Script
Name="Add-CMSRegistration">

    <Param
Name="CMSServer"
Value="" />

    <Param
Name="CMSInstance"
Value="" />

  </Script>

</ScriptConfigs>

DataCenters Section



<DataCenters>

  <!-- This section contains the list of valid data centers and their respective Auto-Install source locations-->

  <DataCenter Name="Data Center 1" Location="Location 1" FilePath="\\alfkidc-2\DataCenter1\AutoInstall\\cf0 " />

  <DataCenter Name="Data Center 2" Location="Location 2" FilePath="\\alfkidc-2\DataCenter2\AutoInstall\\cf0 " />

</DataCenters>

SqlVersions Section

<Version
Name="SQL2008">

  <ConfigurationTemplate
Name="Configuration_2008.ini"
Category="SQLSERVER2008" />

  <ProductStrings>

    <ProductString
Name="Default"
Value="SQLENGINE,REPLICATION,FULLTEXT,CONN,BC,SSMS,ADV_SSMS" />

    <ProductString
Name="DefaultPlusIS"
Value="SQLENGINE,REPLICATION,FULLTEXT,BIDS,CONN,IS,BC,SSMS,ADV_SSMS" />

    <ProductString
Name="Minimal"
Value="SQLENGINE,CONN,BC,SSMS,ADV_SSMS" />

    <ProductString
Name="Full"
Value="" />

  </ProductStrings>

  <Editions>

    <Edition
Name="Standard"
Key=""
FolderName="SQL2008\Standard" />

    <Edition
Name="Enterprise"
Key=""
FolderName="SQL2008\Enterprise" />

  </Editions>

  <TemplateOverrides>

    <Setting
Name="SQLSYSADMINACCOUNTS"
Value='"alfki\SQL_DBA" "alfki\SQL_Ops"' />

    <Setting
Name="INSTALLSQLDATADIR"
Value="C:\SystemDbs" />

    <Setting
Name="SQLBACKUPDIR"
Value="C:\Backups" />

    <Setting
Name="SQLUSERDBDIR"
Value="C:\Data" />

    <Setting
Name="SQLUSERDBLOGDIR"
Value="C:\Logs" />

  </TemplateOverrides>

</Version>

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

5) Run the SQL SPADE Helper application to build the SQL Server installation folders - Launch the SqlSpadeHelper.exe application located in the Tools folder where you unzipped SPADE

Click on the “…” button and browse to the Run-Install.config file

Select the Data Center that you want to build the folder structure for and then click the Check button

For each entry that is missing or empty, select the row and select the operation to perform

1) None – take no action

2) Create Folder – create the folder, but leave it empty

3) Populate Folder – create and populate the folder from the media source

Click on the Build Folders button

7) Review the scripts in the PreScripts and PostScripts folders to ensure that they meet your needs

Updated Wiki: Configuring SQL Scripted PowerShell Automated Deployment Engine (SPADE)

sarasotasql — Sat, 24 Sep 2011 20:38:38 GMT

1) Download the latest release from http://sqlspade.codeplex.com

3) Unzip the file (preferably to a network share)

4) Edit the Run-Install.config file for your configuration

AppSettings Section

<!-- This section contains default settings to be used for all installs - these can be overridden
-->

<AppSettings>

  <Setting
Name="WindowsScriptsFolder"
Value="C:\Windows\Script"/>

  <Setting
Name="FilePath"
Value="S:\Tools"/>

</AppSettings>

The AppSettings section contains basic configuration options that apply to the process, and are not a specific version of SQL.

1) WindowsScriptsFolder – this setting defines the folder on the destination server that hold any scripts located in the PowerShellScripts folder

2) FilePath – defines the default working folder used to copy all of the setup files to the destination server

ScriptConfigs Section

<!-- This section contains settings used by individual pre/post scripts - these must be reviewed and set
-->

<ScriptConfigs>

  <Script
Name="Verify-AdminGroup">

    <Param
Name="Domain"
Value="" />

    <Param
Name="Group"
Value="" />

  </Script>

  <Script
Name="Check-AncillaryServices">

    <Param
Name="Services"
Value="" />

  </Script>

  <Script
Name="Verify-MgmtServerAccess">

    <Param
Name="Servers"
Value="" />

  </Script>

  <Script
Name="Resize-TempDB">

    <Param
Name="MaxFileCount"
Value="8" />

    <Param
Name="MaxFileInitialSizeMB"
Value="1024" />

    <Param
Name="MaxFileGrowthSizeMB"
Value="2048" />

    <Param
Name="FileGrowthMB"
Value="512" />

    <Param
Name="CoreMultiplier"
Value="1" />

  </Script>

  <Script
Name="Add-CMSRegistration">

    <Param
Name="CMSServer"
Value="" />

    <Param
Name="CMSInstance"
Value="" />

  </Script>

</ScriptConfigs>

DataCenters Section



<DataCenters>

  <!-- This section contains the list of valid data centers and their respective Auto-Install source locations-->

  <DataCenter Name="Data Center 1" Location="Location 1" FilePath="\\alfkidc-2\DataCenter1\AutoInstall\\cf0 " />

  <DataCenter Name="Data Center 2" Location="Location 2" FilePath="\\alfkidc-2\DataCenter2\AutoInstall\\cf0 " />

</DataCenters>

SqlVersions Section

<Version
Name="SQL2008">

  <ConfigurationTemplate
Name="Configuration_2008.ini"
Category="SQLSERVER2008" />

  <ProductStrings>

    <ProductString
Name="Default"
Value="SQLENGINE,REPLICATION,FULLTEXT,CONN,BC,SSMS,ADV_SSMS" />

    <ProductString
Name="DefaultPlusIS"
Value="SQLENGINE,REPLICATION,FULLTEXT,BIDS,CONN,IS,BC,SSMS,ADV_SSMS" />

    <ProductString
Name="Minimal"
Value="SQLENGINE,CONN,BC,SSMS,ADV_SSMS" />

    <ProductString
Name="Full"
Value="" />

  </ProductStrings>

  <Editions>

    <Edition
Name="Standard"
Key=""
FolderName="SQL2008\Standard" />

    <Edition
Name="Enterprise"
Key=""
FolderName="SQL2008\Enterprise" />

  </Editions>

  <TemplateOverrides>

    <Setting
Name="SQLSYSADMINACCOUNTS"
Value='"alfki\SQL_DBA" "alfki\SQL_Ops"' />

    <Setting
Name="INSTALLSQLDATADIR"
Value="C:\SystemDbs" />

    <Setting
Name="SQLBACKUPDIR"
Value="C:\Backups" />

    <Setting
Name="SQLUSERDBDIR"
Value="C:\Data" />

    <Setting
Name="SQLUSERDBLOGDIR"
Value="C:\Logs" />

  </TemplateOverrides>

</Version>

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

5) Run the SQL SPADE Helper application to build the SQL Server installation folders - Launch the SqlSpadeHelper.exe application

Click on the “…” button and browse to the Run-Install.config file

Select the Data Center that you want to build the folder structure for and then click the Check button

For each entry that is missing or empty, select the row and select the operation to perform

1) None – take no action

2) Create Folder – create the folder, but leave it empty

3) Populate Folder – create and populate the folder from the media source

Click on the Build Folders button

7) Review the scripts in the PreScripts and PostScripts folders to ensure that they meet your needs

Updated Wiki: Documentation

sarasotasql — Sat, 24 Sep 2011 20:38:18 GMT

Configuring SQL Scripted PowerShell Automated Deployment Engine (SPADE)

Updated Wiki: Configuring SQL Scripted PowerShell Automated Deployment Engine (SPADE)

Sarasotasql — Sat, 24 Sep 2011 20:33:51 GMT

1) Download the latest release from http://sqlspade.codeplex.com

3) Unzip the file (preferably to a network share)

4) Edit the Run-Install.config file for your configuration

AppSettings Section

<!-- This section contains default settings to be used for all installs - these can be overridden
-->

<AppSettings>

  <Setting
Name="WindowsScriptsFolder"
Value="C:\Windows\Script"/>

  <Setting
Name="FilePath"
Value="S:\Tools"/>

</AppSettings>

The AppSettings section contains basic configuration options that apply to the process, and are not a specific version of SQL.

1) WindowsScriptsFolder – this setting defines the folder on the destination server that hold any scripts located in the PowerShellScripts folder

2) FilePath – defines the default working folder used to copy all of the setup files to the destination server

ScriptConfigs Section

<!-- This section contains settings used by individual pre/post scripts - these must be reviewed and set
-->

<ScriptConfigs>

  <Script
Name="Verify-AdminGroup">

    <Param
Name="Domain"
Value="" />

    <Param
Name="Group"
Value="" />

  </Script>

  <Script
Name="Check-AncillaryServices">

    <Param
Name="Services"
Value="" />

  </Script>

  <Script
Name="Verify-MgmtServerAccess">

    <Param
Name="Servers"
Value="" />

  </Script>

  <Script
Name="Resize-TempDB">

    <Param
Name="MaxFileCount"
Value="8" />

    <Param
Name="MaxFileInitialSizeMB"
Value="1024" />

    <Param
Name="MaxFileGrowthSizeMB"
Value="2048" />

    <Param
Name="FileGrowthMB"
Value="512" />

    <Param
Name="CoreMultiplier"
Value="1" />

  </Script>

  <Script
Name="Add-CMSRegistration">

    <Param
Name="CMSServer"
Value="" />

    <Param
Name="CMSInstance"
Value="" />

  </Script>

</ScriptConfigs>

DataCenters Section



<DataCenters>

  <!-- This section contains the list of valid data centers and their respective Auto-Install source locations-->

  <DataCenter Name="Data Center 1" Location="Location 1" FilePath="\\alfkidc-2\DataCenter1\AutoInstall\\cf0 " />

  <DataCenter Name="Data Center 2" Location="Location 2" FilePath="\\alfkidc-2\DataCenter2\AutoInstall\\cf0 " />

</DataCenters>

SqlVersions Section

<Version
Name="SQL2008">

  <ConfigurationTemplate
Name="Configuration_2008.ini"
Category="SQLSERVER2008" />

  <ProductStrings>

    <ProductString
Name="Default"
Value="SQLENGINE,REPLICATION,FULLTEXT,CONN,BC,SSMS,ADV_SSMS" />

    <ProductString
Name="DefaultPlusIS"
Value="SQLENGINE,REPLICATION,FULLTEXT,BIDS,CONN,IS,BC,SSMS,ADV_SSMS" />

    <ProductString
Name="Minimal"
Value="SQLENGINE,CONN,BC,SSMS,ADV_SSMS" />

    <ProductString
Name="Full"
Value="" />

  </ProductStrings>

  <Editions>

    <Edition
Name="Standard"
Key=""
FolderName="SQL2008\Standard" />

    <Edition
Name="Enterprise"
Key=""
FolderName="SQL2008\Enterprise" />

  </Editions>

  <TemplateOverrides>

    <Setting
Name="SQLSYSADMINACCOUNTS"
Value='"alfki\SQL_DBA" "alfki\SQL_Ops"' />

    <Setting
Name="INSTALLSQLDATADIR"
Value="C:\SystemDbs" />

    <Setting
Name="SQLBACKUPDIR"
Value="C:\Backups" />

    <Setting
Name="SQLUSERDBDIR"
Value="C:\Data" />

    <Setting
Name="SQLUSERDBLOGDIR"
Value="C:\Logs" />

  </TemplateOverrides>

</Version>

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

5) Run the SQL SPADE Helper application to build the SQL Server installation folders - Launch the SqlSpadeHelper.exe application

Click on the “…” button and browse to the Run-Install.config file

Select the Data Center that you want to build the folder structure for and then click the Check button

For each entry that is missing or empty, select the row and select the operation to perform

1) None – take no action

2) Create Folder – create the folder, but leave it empty

3) Populate Folder – create and populate the folder from the media source

Click on the Build Folders button

7) Review the scripts in the PreScripts and PostScripts folders to ensure that they meet your needs