Creating a SQL Server 2008 SysPrep Image

Starting with SQL Server 2008 R2 Microsoft has added the SysPrep feature to the SQL Server setup, in this way you can now have a server or workstation image with SQL already installed, to create the image you must copy the setup files into the local disk, then when you run the setup you will see a new option among the already known ones:

image

What you need to do now is follow the setup wizard and at the end execute the sysprep utility. After you have cloned you machine and ran the sysprep mini setup you will see an option to finish the SQL Server configuration, as shown in the following image:

 

image

There are some limitations as peteras pointed (http://blogs.msdn.com/petersad/archive/2009/12/17/sql-server-2008-r2-sysprep-step-by-step.aspx) out on his blog:

 

  1. Only the database engine and reporting services supports Sysprep
  2. Cannot be used for clustering scenarios
  3. Not supported on IA64 system or supported in WOW64
  4. The installation media need to be available when preparing an image and configuring the image. When Sysprepping a SQL Server Express, you need to extract the files to the local machine before preparing the image.

 

More detailed step can be found here http://msdn.microsoft.com/en-us/library/ee210754(SQL.105).aspx

 

Regards,

 

Ing. Eduardo Castro Martínez, PhD – Microsoft SQL Server MVP

http://mswindowscr.org

http://comunidadwindows.org

Costa Rica

Technorati Tags: SQL Server

LiveJournal Tags: SQL Server

del.icio.us Tags: SQL Server

http://ecastrom.blogspot.com

http://ecastrom.wordpress.com

http://ecastrom.spaces.live.com

http://universosql.blogspot.com

http://todosobresql.blogspot.com

http://todosobresqlserver.wordpress.com

http://mswindowscr.org/blogs/sql/default.aspx

http://citicr.org/blogs/noticias/default.aspx

http://sqlserverpedia.blogspot.com/

Comments

Popular posts from this blog

Desempeño de SQL Server 2008 R2 y Max Worker Threads

Cómo identificar consultas más pesadas en SQL Server

SQL Server La longitud de los datos LOB (2200100) que se van a replicar excede el máximo configurado 65536.