Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

My product installation does an unattended install of SQL Server (SQL Server Express by default). I use command line arguments rather than a configuration file, so I'm quite familiar with this process.

This unattended install occurs on the same machine that my install media is running on. However I need to look at installing the SQL Server instance on a separate machine to what the install media is running on. The target machine will be on the same network.

Is it possible to do this unattended? If so, is it simply extra command line arguments or is it a different process (i.e. a PowerShell script)?

share|improve this question

2 Answers 2

@MaxVermon mentioned PSExec.exe from sysinternals as a good way to spawn installation on a remote machine.

I would suggest to use : Scripted PowerShell Automated Deployment Engine (SPADE) for SQL Server.

From codeplex :

SPADE simplifies the process of standing up a new SQL Server instance by applying standard Operating System pre-configurations, Installing SQL Server and then applying post-configurations and creating standard objects.

SPADE is a tool that is designed to speed up your standard deploymets of SQL Server. You may be saying "But I can already do an unsattended install"...but that's not all that's involved in most server builds. There are Operating System configurations like Microsoft Distrubuted Transaction Coordinator (MSDTC), Local Security Policy and others. I'm sure that you also have standard SQL objects that need to be deployed like Stored Procedures, Agent Jobs, Operators, etc. All of this can be done by SPADE automatically by running 1 simple PowerShell script.

Every organization is different, so this tool has been built so that it can easily be customized without requiring you to be a master of PowerShell. A simple XML configuration file defines the options for your standard build. For those non-standard, or "one-off" builds, the script has been defined so that you can change things for a single build without having to change the configuration file.

The current release supports standalone installs of SQL 2005, 2008, 2008R2, and "Denali".

Kevin Kline has a good post on Free Tool Review: Scripted PowerShell Automated Deployment Engine

share|improve this answer
    
Great suggestion, I'm going to spend a little time reviewing and digesting this one. –  slugster Oct 1 '13 at 2:46
    
+1 for cool tool recommendation. –  Max Vernon Oct 1 '13 at 4:48

To perform unattended install to a remote machine you should consider providing a separate installation option that allows just the database engine to be installed on a machine, and forget about doing it remotely. Remote installation will be very difficult to troubleshoot and is not transparent for the installing individual.

Having said that you could look at using SysInternals PSexec.exe to remotely spawn the unattended install.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.