AutoConfig Overview

Previous AutoConfig Processing	AutoConfig Execution Next

SQL FineBuild can automatically execute site-specific routines during the install process, providing they are located in specific folders. This section provides an overview of what can be processed and where the files can be located.

SQL FineBuild uses the following parameters to help AutoConfig processing:

Parameter	Default Value	Description
/SetupAutoConfig:	Yes	Controls whether AutoConfig processing is done
/PathAutoConfig:	(blank)	If blank then a folder from Supported File Locations is used, otherwise the specified folder is used

Supported File Types

The file types that can be processed by SQL FineBuild are:

Item	Description
.BAT	DOS-Style Batch Files
.CMD	DOS-Style Batch Files
.PS1	Powershell Modules
.MSI	Windows Installer Modules
.MSP	Windows Installer Modules
.MSU	Windows Installer Modules
.EXE	Windows Programs
.SQL	T-SQL Files
.JS	Windows Script Host JavaScript Modules
.VBS	Windows Script Host VBScript Modules
.WSF	Windows Script Host Modules

Note: The ability to process .SQL files allows the creation of Logins, Databases, Permissions, etc to be automated.

There is no possibility of supplying user-defined parameters to the execution process. If it is required to provide parameters then it is suggested that a .BAT or .PS1 file is created that can pass the parameters, and the target file is stored in a sub-folder of the \AutoConfig folder.

Supported File Locations

If /PathAutoConfig: is blank, SQL FineBuild will look for a folder called \AutoConfig in one of two places, and will use the first \AutoConfig folder it finds:

Search Order	Location
1	The folder from which the SQL FineBuild process is started. It is recommended that this should be the Site SQL Files Folder
2	The \Additional Components folder. This location is not recommended but can be used

SQL FineBuild will also search sub_folders of the \AutoConfig folder. This is to allow server-specific components to be processed.

The sub-folders that are searched are described below. SQL FineBuild will always look for all of these folders, but it is expected that each organisation will only use those that are relevant to their requirements:

Sub Folder	Description
(Server Name)	A sub-folder with the same name as the server hosting SQL Server
(Cluster Name)	For a SQL Server Cluster Install, the name of the Windows Cluster hosting the Windows Server nodes
(Availability Group)	For a SQL Server Always On Install, the name of the AG hosting the SQL Server nodes
(Distributed Availability Group)	Where a Distributed Availability Group is specified for a SQL Server Always On Install, the name of the group
\SQLTools	For any build with /SetupSQLTools:YES the \SQLTools sub-folder will be searched
(SiteRole)	A sub-folder with the value of the /SiteRole: parameter will be searched

SQL FineBuild will process all components in a given folder before searching the next folder in the sequence. No further sub-folders will be searched.

Note: A sub-folder of the (Server Name) folder called \Documentation will be created if it does not already exist. This will hold the Setup Kerberos command file and a copy of the SQL FineBuild Configuration Report File. It is suggested that any other server-specific documentation created by the DBA Team is also stored in this folder.

Copyright FineBuild Team © 2021. License and Acknowledgements

Previous AutoConfig Processing	Top	AutoConfig Execution Next