Add New SQL Server Version

Previous FineBuild State File	Add New Windows Version Next

This section details the steps needed to add a new SQL Server Version to SQL FineBuild.

The details shown take the form of a worked example for the addition of SQL Server 2022 to SQL FineBuild. A similar process can be used to further upgrade SQL FineBuild when the version following SQL 2022 is releases.

This process consists of the following steps:

• Setup SQL Version Folder
• Configuration File Changes
• FBConfigBuild Changes
• Exploiting New SQL Server Features

Top

---

Setup SQL Version Folder

A folder must be set up to hold the SQL FineBuild and Microsoft install media for the new SQL Server version.

1. Copy the high-level folder for the most recent version of SQL Server

   Give it the name of the new SQL Server version.

   For example, copy the SQL FineBuild SQL2019 folder and call it SQL2022. The folder for the most recent version should be used as there will be fewer changes needed to support the new SQL Server version

   screenshot to be added

2. Delete files relating to the old SQL Server version install media

   Navigate to the new folder and delete all the sub-folders for the previous SQL Server version

   Navigate to the _\Service Packs\RTM _ sub-folder of the new folder and delete all files

3. Prepare the Config.xml file for the new SQL Version

   Navigate to the new \FineBuild folder

   Rename the Config.xml file to match the new version of SQL Server

   For example, rename SQL2019Config.xml to SQL2022Config.xml

   screenshot to be added

Top

---

Configuration File Changes

The FineBuild Configuration File must be changed for the new SQL Server version. Edit the Config.xml file using a text editor such as NotePad.

1. Set High-Level Config Key

   Change the key to match the new version of SQL Server

   For example, change to

2. <Global key changes

   Only one or two changes are normally needed for attributes held under the <Global key

   • Set Service Pack level

     If a beta release of the new SQL Server version is being used, set the SPLevel attribute to the relevant pre-release version

     For example, change the value of SPLevel from "RTM" to "CTP1", and also create a sub-folder of the \Service Packs folder also called CTP1

     The SPLevel attribute should be changed to "RTM" when the new SQL Server version is formally released

   • Set Cumulative Update level

     The value of the SPCULevel key should be set to "CU1"

     The value of the SPCULevel key should be changed to match the latest CU number as Cumulative Updates are released

3. <Strings key changes

   A number of changes and additions will be needed for attributes held under the <Strings key:

   • Add new SQL Menu item

     Duplicate the menu item for the most recent version of SQL Server

     Change the attribute name for the menu item to match the new version of SQL Server

     Update the menu text to match the name used by the new version of SQL Server

   • CLSid Attribute changes

     Some of the CLSId attributes will need to be reviewed and changed where necessary:

     CLSIdDRUCtlr CLSIdDTExec CLSIdSQL CLSIdSQLSetup CLSIdSSIS
     

     It can be difficult to find the new values. The best way is to install the new version of SQL Server then use the DCOM Component snap-in for the Management Console to find the new CLSId values

   • Report Service attribute changes

     The values for the following Report Service attributes will need to be reviewed and changed where necessary:

     RsFxVersion RSVersionNum ReportViewerVersion
     

   • SSIS Attribute changes

     The values for the following SSIS attributes will need to be reviewed and changed where necessary:

     InstIS InstISMaster InstISWorker
     

     For example, change the value for the InstIS attribute from "MSDtsServer150" to "MSDtsServer160"

   • SQL Server Attribute changes

     The values for the following will will need to be reviewed and changed where necessary:

     NativeOS SQLVersionNet SQLVersionNum SQLVersionWMI VSVersionNum VSVersionPath
     

     For example, change the value for the SQLVersionNum attribute from "150" to "160"

4. <Files key changes

   A number of attributes held under the <Files key need to be removed.

   Remove all attributes and their values that are used to define Cumulative Updates. These will be in the form:

   RTMX64CU1 RTMX64CU2 etc
   

   These attributes will need to be added back into the Configuration file along with the values for the new CU files as Cumulative Updates are released for the new SQL Server version

Top

---

FBConfigBuild Changes

To be completed

Top

---

Exploiting New SQL Server Features

To be completed

Top

---

Copyright FineBuild Team © 2021. License and Acknowledgements

Previous FineBuild State File	Top	Add New Windows Version Next