Quantcast
Channel: SQL Server Setup & Upgrade forum
Viewing all articles
Browse latest Browse all 7696

SQL Server 2017 install command line vs configuration.ini file

$
0
0

I need to install 10 SQL Server 2017 Ent Edn instances on a new AlwaysOn cluster which has two HA nodes and one remote DR node.  So that would be treated as three stand-alone servers, each with ten instances, for a total of 30 instances.  Right so far?  (For now, I'm only concerned with the SQL instance installs, not AlwaysOn configuration or other pre/post-install tasks.)  I will be installing the database engine and not SSAS, SSRS, and other advanced features, so the instance footprints will be pretty straightforward.  The most I'll be diverging from defaults is to change all the instance-specific folder paths and of course, the instance names.  (Shared file locations will be default.)

What is the practical difference between command line install vs configuration.ini file as far as ease of use, limitations, flexibility, etc.  For example, can all possible command line parameters also be used in a configuration.ini file? 




Viewing all articles
Browse latest Browse all 7696

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>