/build/static/layout/Breadcrumb_cap_w.png

Install SQL Server 2016 for 300 machines

Hello,

I need to install SQL Server 2016 for almost 300 machines. I have SCCM 2012 running in the company.

If was just a simple defaults instalations in the 300 machines there is no problem, but I have an instance name for each one. ex:machine 1 - instance name 1; machine 2 - instance name 2; etc..... 


I can configure in SCCM a program like this:

Setup.exe" /ACTION=Install /q /IACCEPTSQLSERVERLICENSETERMS /IACCEPTROPENLICENSETERMS /FEATURES=SQLENGINE,FULLTEXT,CONN,IS,SNAC_SDK,BOL /INSTANCENAME="instancename"  /AGTSVCACCOUNT="NT AUTHORITY\Network Service" /SQLSVCACCOUNT="NT Authority\System" /SQLSYSADMINACCOUNTS="user1" "user2" "user3" "user4" /ISSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE"

How do I modify this script to program read the machine name and fill the parameter /INSTANCENAME with the INSTANCENAME for that machine name?


Create a powershell script? Have a csv file with MACHINE NAME;INSTANCE NAME? Create a vbs? Any idea, sugestion?


Thks

JLV





0 Comments   [ + ] Show comments

Answers (3)

Posted by: anonymous_9363 7 years ago
Red Belt
0
Errrr...why? Why wouldn't you create a server, install SQL Server on it and point your users at that?

And even if you do need separate installations, why do you think you need separate instance names? If the individual boxes are going to host database(s), then users will simply connect to \\[name_of_box]\[instance name].
Posted by: j23_123 7 years ago
White Belt
0
I want to depoly for 300 servers with sccm package.
Posted by: anonymous_9363 7 years ago
Red Belt
0
It's always good to get the full story AFTER one has replied [eyes wide]

Anyway...the same applies. The server name - exactly like a workstation name - is unique: no need for separate instance names.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ