180 likes | 323 Views
Lean and Mean: SQL Server on Windows Server Core. Argenis Fernandez Senior Database Monkey SurveyMonkey. About your Speaker today…. SQL Server is an app. An application that runs on top of Windows. Internet Explorer on a production server? Really?
E N D
Lean and Mean: SQL Server on Windows Server Core Argenis Fernandez Senior Database Monkey SurveyMonkey
SQL Server is an app. An application that runs on top of Windows. Internet Explorer on a production server? Really? Next thing you know you’ll want an antivirus for your server. Oh, wait… Remember that the best practice is to have single-purpose servers on any given topology
Why would you want to use Server Core? • The obvious: • Smaller footprint on disk: ~84% (incl. SQL) • Less patches needed: ~45% • Boots faster = less downtime • Reduced surface area = better security • _Maybe_ better performance • <Insert marketing speak here for TCO> Source: Allan Hirt (@SQLHA), DBI313, TechEd 2012
Why would you want to use Server Core? • The not so obvious: • It forces you out of your comfort zone (this is a good thing!) • Think scripting, and automation. E.g., Powershell • Setup takes a lot less time (less than 20 minutes on a VM) • You probably won’t consider RDPing into the server
Not ready to jump? Consider MinShell • A lot of benefits of Server Core • Can still run GUI administration tools • No desktop-like UI • You can actually switch back and forth between Full GUI, MinShelland Server Core – but once you install SQL, you can’t switch anymore. You’d have to uninstall SQL beforehand.
SQL Server Support for Server Core OS: Windows Server 2008 R2 SP1 or 2012 Cannot install 32-bit instances of SQL (no WOW64) All non-GUI based features of SQL supported. Not supported: SSRS, SSDT, Client Tools Backward Compatibility, Client Tools SDK, BOL, Distributed Replay Controller, MDS, DQS.
SQL Setup A quick and easy way: run wizard on a GUI server, then save the configuration file. The more advanced ways: Command line Configuration file
And now for the best slide of this talk D:\setup.exe /ACTION="Install" /ERRORREPORTING=0 /FEATURES=SQLEngine,Replication /UPDATEENABLED=0 /INSTANCENAME=MSSQLSERVER /AGTSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" /SQLSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" /SQLSYSADMINACCOUNTS="SQL\Argenis Fernandez" /Q /SQMREPORTING=0 /BROWSERSVCSTARTUPTYPE="Disabled" /SECURITYMODE="SQL" /SAPWD="SQLF@m1ly2013%" /SQLSVCSTARTUPTYPE="Automatic" /TCPENABLED=1 /IACCEPTSQLSERVERLICENSETERMS
Things you should know You should install .NET 3.5 SP1 manually dism /online /enable-feature /all /featurename:NetFx3 /source:d:\sources\sxs You might be okay with disabling Windows Firewall netshadvfirewall set allprofiles state off
Clusters and Availability Groups Things you should know.
Resources • Allan Hirt – (SQLHA.com) DBI303, TechEd 2012 • Configure SQL Server 2012 on a Server Core Installation • Configuring AlwaysOn with SQL Server Powershell
Coming up… #SQLBITS