Survey: SQL Express 2008 and Patching

We are working on the patching model that will be used for SQL Server 2008 Express and we're considering a change that I wanted to get your feedback on. Please take a moment to answer a few questions; feel free to answer through a comment to this post or by clicking the EMAIL link at the top of the blog.

  1. We are considering separating the patching process from the new install process such that the SQL Express package (such as SQLEXPR_x86_ENU.exe) would be used for new installations of the most current service release and patching of existing installations would be done using the same patch as the rest of SQL Server 2008. (Historically we have created a single installer package for SQL Express that could both install a new instance and update an existing instance.) Is this a good or bad plan? (Why?)
  2. What would the impact to you or your company be if we choose the model that doesn't work for you? (i.e. How many installs are impacted? Would you have to re-write your application installer? Etc.)
  3. If the new model causes the SQL Express package to grow, is that a major concern for your scenario? (How much could it grow by % without concerning you?)    

    Thanks for your feedback on this.

    - Mike

Comments (2)

  1. MichaelGG says:

    We don’t do much automatic SQL Express stuff. It’s mainly installed direct on servers we need, or pre-installed on a server we ship. (Mainly using it where a full SQL license isn’t available.) Even so, it’d be nice to use the same patches SQL Server uses.

  2. An always up-to-date SQL Express package (w/ current Cumulative Update) that can install and update SQL Express?

    Great to be included in applications as a prerequisite.

    Cumulative Updates and Service Packs that support patching SQL Express?

    Great to maintain existing heterogenous environments with a single download.

    Having it both and the story straight for Business Intelligence Studio?


Skip to main content