Happy New Year!


I hope you had a safe and happy holiday season.  To help ring in the new year I have published a new update to the SQL SPADE open source project found at http://sqlspade.codeplex.com.  This update furthers the SQL 2012 support added in the 1.1 release by now supporting installs of SQL 2012 on Windows Server Core.  I feel that this is one of the biggest areas of benefit for SPADE considering the steep learning curve that you face when you start working with Server Core.  You don’t realize just how much you rely on graphical tools and wizards until they’re gone.  Running SPADE turns installing SQL Server into running a single PowerShell function, no GUI needed.

Along with the support for Server Core, the following enhancements have been make to SPADE release 1.2:

  • Added QtWeb (Open Source) standalone browser for viewing the SQL SPADE log on Server Core – I still prefer this over writing the log to a plain text file that would have to be searched for errors
  • Changed the Set-SqlTcpPort logic to use the WMI method because the registry method was inconsistent when installing SQL 2012 on Server Core 
  • Fixed the exists check in the VerifyAdminGroup script to look for the fully qualified domain group
  • Fixed a logic error in the Execute-SqlCommand function that was masking exceptions when the SQL connection failed
  • Added support for excluding scripts by putting an “_” at the beginning of the file name – when a script is excluded the install will log that the script is being skipped because it has been marked as excluded
  • Changed the ConfigureDatabaseMail script to a PowerShell script that uses external configurations stored in the Run-Install.config file – this change was to enforce the pattern of all script variables being centralized in the configuration file and simplifies implementation for new environments 
  • Changed the order for the RemoveBuiltinAdminsLogin script – moved this script to the end of the process so it is not executed in the event of a critical failure
  • Changed the order for the Restart-SqlService script – moved this to the end of the process because the time needed to restart the service could cause failures in subsequent SQL scripts

I have also added script management functionality to the SqlSpadeHelper tool.  Watch here for an upcoming article that details how to use it to manage your scripts.

Leave a Reply

Your email address will not be published. Required fields are marked *