Unattended installations of SQL Server 2008 R2 - by Fredrik Vestin

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 648248 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 2/28/2011 2:17:27 AM
Access Restriction Public


The SQL Server 2005 setup.exe allowed the following parameters for unattended installations:

/qb - allows the display of basic Setup dialog boxes. Error messages are also displayed.
/qn - suppresses all Setup dialog boxes and error messages

See http://msdn.microsoft.com/en-us/library/ms144259(v=sql.90).aspx

For SQL Server 2008 R2 however, these parameters are no longer supported but the following are used instead:

/Q - Specifies that Setup runs in a quiet mode without any user interface. This is used for unattended installations.
/QS - Specifies that Setup runs and shows progress through the UI, but does not accept any input or show any error messages.

See http://msdn.microsoft.com/en-us/library/ms144259.aspx

I have some questions regarding this.

1.Why is there no way to have an unattended installer display error messages like the 2005 /qb switch did?
Imagine that you have an installer written in InstallShield for example that launches an unattended setup. With 2005, the SQL Server installation notified the user that the installation failed and what error message it returned. With 2008 the /QS option does not give any error messages at all but you have to dig into the SQL Server setup logs to determine what went wrong. This is not very user friendly. 
2.Why is the /QS installation option in 2008 only available for /ACTION=install and not /ACTION=upgrade? Why would you not want to see the progress of an upgrade just as well as a fresh install? 
3.The dialogs that are displayed with the /QS switch are very similar to the dialogs displayed when doing an interactive installation, except that they don't accept input. At the most theare are no less than THREE dialogs beeing displayed to the end user with some saying "click Install to install..." although the install button is disabled (screenshot). This is not the way an unattended installer should behave.
It would be much better if the entire installation just displayed a small windows saying "Installing SQL Server 2008 R2" or similar and then displayed any errors that occurred during installation. 
4.Is there any way to prevent the command line window displayed when installing with the /Q option? 
Sign in to post a comment.
Posted by simdoc on 5/29/2013 at 6:57 AM
I just filed this one as well for SQL 2012 (https://connect.microsoft.com/SQLServer/feedback/details/788852/allow-for-error-messages-to-be-returned-in-qs-installations-at-least-in-sql-express). In my opinion, this is needed in SQL 2008, but much more in 2012.
Posted by Microsoft on 6/15/2011 at 7:41 AM
Thanks for contacting us:
- There is no plan to support /qb
- /qs in SQL Server code-named "Denali" /qs will be support for nearly all /Actions, more than we supported in SQL Server 2008
- you can hide the command prompt by adding /HideConsole
Posted by Microsoft on 2/28/2011 at 4:17 PM
Hi Fredrik,

Thank you for your feedback. We will look into your suggestions and will be in touch with you as appropriate.

Best regards,
Microsoft SQL Server