Post reply

How useful are saved configuration .ini files for automating installs?

  • July 17, 2014 at 12:36 pm

    #310011

    I nabbed a couple from some recent installs I did, and, assuming I can get my SAN guy to always give drives the same letter assignment, it looks fairly helpful.

    There's still a bunch of additional stuff to do, like turn on instant file initialization, size/create additional tempdb files, and set up alerts and database mail, etc.

    Can the configuration file be expanded to handle any of that? Do you use something else to template/automate your SQL installs? The more I do it, the less I want to keep doing it.

    Thanks

  • July 29, 2014 at 11:52 am

    #1733344

    I think the INI files are useful. You're right, there is a lot more to do after SETUP finishes. Checkout a codeplex tool called SPADE, helps with the rest of the stuff.

  • July 29, 2014 at 12:00 pm

    #1733346

    I tried to run a couple installs recently using the .ini files, but got errors when assigning my service account to the SQL and Agent services because they required passwords. I'll check that tool out.

    Thanks

  • July 30, 2014 at 2:54 am

    #1733491

    As well as SPADE, you might want to look at FineBuild, also on Codeplex.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

  • July 30, 2014 at 5:33 am

    This was removed by the editor as SPAM

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply