1 / 32

Deploying Microsoft SQL Server 2012 Using Windows Server Core

DBI313. Deploying Microsoft SQL Server 2012 Using Windows Server Core. Chuck Heinzelman Senior Program Manager – BPD CX Microsoft. Thomas LaRock Technical Evangelist Confio. Abstract.

page
Download Presentation

Deploying Microsoft SQL Server 2012 Using Windows Server Core

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. DBI313 Deploying Microsoft SQL Server 2012 Using Windows Server Core Chuck Heinzelman Senior Program Manager – BPD CX Microsoft Thomas LaRock TechnicalEvangelist Confio

  2. Abstract • SQL Server 2012 is the first version of SQL Server to support Windows Server Core. Windows Server Core is a good way to increase uptime and reliability—two things all administrators care about. This session discusses how to plan, deploy, and effectively administer SQL Server 2012 using Windows Sever Core, including how to deploy AlwaysOn availability groups.

  3. www.sqlcat.com chuck.heinzelman@ microsoft.com @SQLBoyWonder Chuck Heinzelman

  4. thomaslarock.com sqlrockstar@ thomaslarock.com @sqlrockstar Thomas LaRock IN TRAINING

  5. Why Windows Server Core for SQL Server 2012? • More secure • Less surface area with fewer things installed • Command line a deterrent for many • Less to patch = higher uptime, less risk • Shorter outages • Also noted in KBs • Possibility of slightly better performance • Less “stuff” running, a bit more overhead • Not a guarantee, and won’t be night/day

  6. Overcoming Barriers to Deploying Server Core • It’s different • No, it’s just Windows that is command line-based (and maybe a tad of GUI … more on that in a bit) • Not currently a standard in your company • If base OS version (i.e. W2K8 R2) already is, what’s the blocker? • Lack of administration skills around command line/PowerShell • Arguably biggest risk • Possible Solution: administer remotely and have scripts ready for the rare time(s) you’d need to be on the box • No direct upgrade path from current deployment • No easy answer here

  7. By The NumbersA Patch Tuesday Test • Executed 5/8/12 • Goal: what would an OOB experience be like? • The test: • Create two VMs with W2K8 R2 SP1 • One full OS, one Server Core • No patching done to the OS • Only tweak was to enable the feature for .NET 3.51 • Install SQL Server 2012 • No patches or updates applied during the install – base RTM • Engine ONLY – no SSMS, etc.

  8. The Results • Disk footprint (in KB) • Patches

  9. SQL Server Support for Server Core • Windows Server 2008 R2 with SP1 (or later) • Windows Server 2012 not officially supported for any version of SQL Server (yet) • SQL Server 2012 only • 64-bit; no WOW support (so no 32-bit) • All supported languages, editions • Features supported: http://tinyurl.com/bmozrgw • Engine (w/replication, FTS), Analysis Services, Client Tools Connectivity, SSIS (Server), MS Sync Framework • Not listed: install elsewhere

  10. Windows Server 2008 R2 Installation

  11. Windows Server 2012 Installation

  12. Windows Tips for SQL Deployments • Can switch between Full/MinShell/”Pure” Core • TIP: If start with Core, GUI payloads not installed by default see http://tinyurl.com/cn7ttsm • How SQL will be supported in this scenario is still TBD • If using WSFC, will have to load GUI management payload • W2K8 R2 SP1 – Enable remote management (will also enable .NET 3.5/2.0) - http://tinyurl.com/28h883x • Unbind protocols in W2K8 R2: NVSPBIND http://tinyurl.com/729mr58 • sconfig may be useful for some things if don’t want to write scripts

  13. SQL Server 2012 Install Behavior on Full GUI OS • Have to manually install .NET Framework 3.51 • Will install .NET 4.0 (if necessary)

  14. SQL Server 2012 Install Behavior on Server Core • Will enable/install .NET Framework (3.51 and 4.0) if not already done

  15. WSFC & Server Core 1 • All the same supportability rules GUI or SC except: • W2K8 R2: Cannot mix Core + full OS nodes – one or the other • Windows Server 2012: Can mix Core/MinShell/Full • Feature enabled in two steps: core WSFC feature, tools • Instead of DISM, use PS cmdletInstall-WindowsFeature with IncludeManagementToolsswitch • IncludeManagementToolswill not enable GUI tools on “Pure” SC

  16. WSFC & Server Core 2 • Enabling the feature • Cluster.exe • Deprecated in W2K8 R2, but still there • Not enabled by default in Windows Server 2012 • Should learn PowerShell cmdlets

  17. WSFC & Server Core 2 • Automation Server • Deprecated in Windows Server 2012 • Not enabled by default • Used by SQL Server (FILESTREAM), so recommended to enable

  18. Installing SQL Server 2012 on Server Core 1 • Command line or command file only • Relevant BOL topics • http://tinyurl.com/bmozrgw, http://tinyurl.com/cnft2fm

  19. Installing SQL Server 2012 on Server Core 2 • Need to install things from the feature pack (http://tinyurl.com/7jovob2) in this order: • Shared Management Objects (base for any management utilities) • PowerShell Extensions (will have AG cmdlets) • Command Line Utilities (sqlcmd, BCP)

  20. Installing SQL Server 2012 on Server Core 3 • Ensure TCPENABLED option is set if standalone instance • Enabled by default for FCIs • Utilize UPDATEENABLED and UPDATESOURCE if applicable • Much better, easier than the SQL 2K8/R2 slipstream process

  21. Demo Installing SQL Server on Windows Server Core Chuck Heinzelman

  22. Demo Using PowerShell to Manage SQL Server Thomas LaRock

  23. Demo Configuring AlwaysOn Through PowerShell Chuck Heinzelman

  24. Summary • SQL Server 2012 is ready to use in production today • Start testing with it now – no need to wait for a SP • Windows Server Core is perfect for mission critical SQL Server deployments • Biggest benefits: smaller footprint, less patching, and higher uptime as a direct result of less patching • Outside of some OS administration on the server itself, it’s just SQL Server on Windows • Use your current SQL Server management strategy – should not require many changes outside of initial configuration • Should never log onto box to administer unless necessary anyway

  25. Additional Information • KB327518 - The Microsoft SQL Server support policy for Microsoft Clustering http://support.microsoft.com/kb/327518 • KB943984 – The Microsoft Support Policy for Windows Server 2008 or Windows Server 2008 R2 Failover Clusters http://support.microsoft.com/kb/943984 • KB2545685 – Recommended hotfixes and updates for Windows Server 2008 R2 SP1 Failover Clusters http://tinyurl.com/7r8flpj • SQL Server 2012 Bare Metal Workshop Series http://tinyurl.com/7l66mks • Server Core team blog http://tinyurl.com/7e4rq8o

  26. Related Content • Breakout Sessions (session codes and titles) • DBI01-WRK-R Bare Metal Microsoft SQL Server 2012 Deployment and Management • WSV309 – Deploying Windows Server 2012: From Bare Metal, Server Core, Minimal Server Interface, and More • Find Us • TLC Area – SQL Server

  27. Thank You! http://www.sqlha.com allan@sqlha.com @SQLHA Allan Hirt

  28. DBI Track Resources @sqlserver @TechEd_NA #msTechEd SQL Server 2012 Eval Copy Hands-On Labs Get Certified! mva • Microsoft Virtual Academy

  29. Resources Learning TechNet • Connect. Share. Discuss. • Microsoft Certification & Training Resources http://europe.msteched.com www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet http://microsoft.com/msdn

  30. Evaluations Submit your evals online http://europe.msteched.com/sessions

  31. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related