{"id":14131,"date":"2013-01-28T13:08:00","date_gmt":"2013-01-28T13:08:00","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=14131"},"modified":"2013-01-28T13:08:00","modified_gmt":"2013-01-28T13:08:00","slug":"deploying-application-virtual-machines-just-got-a-whole-lot-quicker","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=14131","title":{"rendered":"Deploying Application Virtual Machines Just Got A Whole Lot Quicker"},"content":{"rendered":"

Several years ago, I first heard Mark Minasi talk about accidental DBAs<\/em>.  The term refers to server administrators\/engineers who find that the vast majority of their Windows Servers either have or use a SQL Server installation.  We were mostly still in a physical world back then, with virtualisation just in its infancy in the industry (as a whole).  Things have moved on since then.  Anyone deploying servers now should be looking at the virtual option first (be it some open cloud, Xen, VMware, or Hyper-V).  Virtualisation seems to encourage server sprawl and that means lots more servers.<\/p>\n

My last experience as a hands-own \u201cown it\u201d engineer was in hosting.  Here\u2019s how a deployment looked:<\/p>\n

    \n
  1. Time to deploy a VM: about 30 seconds in a wizard, and do something else while the files copied<\/li>\n
  2. Customize the OS: about 1-10 minutes<\/li>\n
  3. Install SQL Server: 30-45 minutes (longer if SQL 2008 R2 Reporting was required)<\/li>\n
  4. Install the SQL Server service pack (if not already slipstreamed): 30-45 minutes<\/li>\n
  5. Install the SQL Server service pack cumulative update (if not already slipstreamed): 30-45 minutes<\/li>\n<\/ol>\n

    In my experience, I could lose the guts of a day installing SQL Server if I didn\u2019t have a slipstreamed package, while the VM deployment itself took very little time.<\/p>\n

    \u201cWhy, in a cloud, shouldn\u2019t the user install SQL Server?\u201d<\/em><\/p>\n

    LMAO!  Clouds are like hosting, and I left the hosting business because 80% of the customers made me want to scream at them.  They were clueless: e.g. the guy who opened a helpdesk call to get a DR replication application written for his new SaaS business (selling DR).<\/p>\n

    Not that all of them were like that.  I learned from a few and some were doing very interesting and innovative things.<\/em><\/p>\n

    When it comes to things like SQL Server, the infrastructure people (or system) must do the installation.  But we want to minimize that time.  SQL Server 2012 SP1 CU2 has expanded support for Sysprep<\/a>.  This means that you can optimise the deployment of virtual machines with SQL Server (including service pack and related cumulative update).  For more information you can see:<\/p>\n