Nate Johnson has a script he uses to automate installation of SQL Server on a new server:
We can then use this file in the
ConfigurationFile
argument ofsetup.exe
from the SQL Server install media. To put a little more color on that: the.ini
file is really just a collection of command-line arguments tosetup.exe
; you could also list them all out in-line, but that would be tedious and silly. Here’s a couple major selling points of creating your own config file:
-
Slipstream updates (SP’s, CU’s), instead of having it go out to MSFT update servers (or *aghast* sticking with the original RTM bits, you heathen you!)
-
Specify drive letters / default file locations: sure, this may be considered old-hat if you’re running super slick storage, but I still find it makes management a bit easier if I know where my MDFs, LDFs, TempDB, & backups will always be.
-
Take advantage of 2016’s better TempDB setup options (# files, size & growth)
Read the whole thing.