SQL 2012/2008 seem to be much more problematic to install than SQL 2005. I have a script that I use with my application installer to install a SQL 2008/2012 instance. This script sets all required options including adding /QS to the command line.
I use this script because I don't want the user to have the ability to change the options. However, if an error occurs, I'd like to know the error so I can diagnose the issue. Currently, the script only reports that the install failed, but there
is no feedback to the person running the script as to the failure. The only way is to use the SQL install logs. While for more advanced problems, that is satisfactory, it is not very good for common simple errors. It turns a simple
diagnosis that possibly the person running the install can figure out, to something complex that requires more advanced personnel to diagnose.
For example, I wrap the Spanish SQL express installer in ...
Go to the complete details ...