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.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have been wracking my brain over upgrading SQL Server 2005 to SQL Server 2005 SP4. I have a script for installing new instances of SQL Server for all versions and they all work wonderfully. Problem is, SQL Server 2012 can't upgrade SQL Server 2005 SP3 and below. So, I have to install SP4 to SQL Server 2005, AND THEN upgrade to SQL Server 2012, which is highly annoying.

I need to do this silently via the command line, but I cannot get it to work at all. Here are some samples I tried:


SQLSP4.exe /quiet /instancename="FOOBAR"

Among a couple other variations. I could not find anything online at all. In fact, the one helpful thread ended in saying that Microsoft didn't have any support for this, but I'm not sure about that.

What can be done here? Does anyone have any experience in updating service packs via command line?

share|improve this question

Make sure you include the /IAcceptSQLServerLicenseTerms switch, otherwise your installation will fail. I have commonly done silent installs of service packs to using the following syntax:

.\<SQLServicePack>.exe /q /action=patch /instancename="FOOBAR" /IAcceptSQLServerLicenseTerms

Full syntax documented here.

share|improve this answer
That syntax is from sql server 2008. I was also under the impression that sql 2005 didn't mandate the licenseterms flag. – Cerealkiller050 Mar 6 '13 at 23:05
This would be my first check, as I've needed that switch whenever I've applied a service pack from the command line. Otherwise, you should look for whatever detail is in the setup log (..\Microsoft SQL Server\90\Setup Bootstrap\Log) for details on the failure. – Mike Fal Mar 6 '13 at 23:14
Thanks for the log. I will check that out now and see what exception was thrown. – Cerealkiller050 Mar 6 '13 at 23:19
Ok, its complaining about invalid command line argument. SQLEXPR4.exe /qb /IACCEPTSQLLICENSETERMS /instancename="FOOBAR". That looks fine to me. – Cerealkiller050 Mar 6 '13 at 23:38
Got a weird help file that came up. Looks like the correct syntax is: SQLEXPR4.EXE /qb /update <update1.msp>. Question is: what is a msp file, and do i have to download it in order to finally get this done? – Cerealkiller050 Mar 7 '13 at 0:01

Your Answer


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.