As a SQL Solution Architect I need to keep abreast of the latest and greatest SQL offerings from Microsoft. Given SQL 2016 has just been release to manufacture, and I’ve a few hours to kill between work and study, I thought it was time to build a virtualised SQL 2016 environment for testing and troubleshooting.
During the installation process I took note of the OS and SQL 2016 hard disk capacity consumed for the most common services (the SQL Feature Selection panel tells you how much hard disk capacity you’ll need for each feature you enable – see below screen shot for an example). For those of you about to embark on setting up your own virtualised SQL 2016 lab, my findings might be of use in keeping your Virtual Machine vmdk files as small as possible (as I don’t have a lot of hard disk space to play with). Besides, it’s always easy to expand the storage after building your VM, but much hard to shrink it.
|14.32 GB||1.58 GB free on a 16 GB C: drive|
|OS||8.81 GB||Without .NET 3.5. With PowerShell 2.0|
|OS||0.77 GB||With .NET 3.5 (and therefore .NET 2.0 and .NET 3.0). With PowerShell 3.0 @|
|SQL||2.08 GB||DBE, Agent, Client Tools Connectivity (inc Visual Studio 2010 Redistributables and .NET 4.6 Framework)|
|SQL||2.66 GB||SSMS #|
@ Yes, you still need to install .NET 3.5 via Server Manager (grrrr); if you don’t SQL will complain during the install process (as it’s always done), costing you time as you back-track.
# SSMS requires a separate installation file now, as it does for Azure as per Microsoft’s stated ‘Cloud First’ strategy; it is no longer a ‘feature’ option during the SQL install process. You’ll need to download SQL 2016 SSMS separately (825 MB file). It can be used to administer SQL Server 2008 to 2016 installations only (all editions).
Additional HDD Consumption by SQL Features
|SQL||0.97 GB||SSRS (Native)|
Notice the feature changes from SQL 2012 and SQL 2014? SSMS is missing but PolyBase and advanced analytics has made the cut …
… and the new Instant File Initialization enabler (aka Volume Maintenance Task)
I always put IFI and LPM (Lock Pages in Memory) in to an AD Security Group and apply that to my SQL Server OU via a GPO so this new feature isn’t a biggy for me.
… and the new TempDB tab.
It will automatically detect how many Cores you have and create up to 8 tempdb files all the same size with best practice fixed auto-growth.
Initial size is limited to 265MB (I believe because anything larger will have a negative impact on the installation time) so you’ll still need to modify this after installation if you require larger tempdb files.
Trace Flags 1117 and 1118 are not required for tempdb anymore.
Read more about how to Install SQL Server 2016 from the Installation Wizard on Microsoft’s MSDN site.
SQL Server Installation Center
SSMS, SSDT, MAP and other tools can be installed from the SQL Server Installation Center (they require you to have access to the internet). I downloaded these once and placed them on a network share.
SQL 2016 Version and Build Info
Here’s the version and build info for SQL 2016 RTM Dev Edn x64 after installation …
- I’m using VMware Workstation 12 as my hypervisor, sitting on top my desktop PC (Intel i7, 2.4GHz, 8 Cores, 8 GB RAM, SSD + spindles).
- 1x PDC, 2x SQL 2016 Dev Edn (which is the same as the Enterprise Edition).
- All 3 VMs are using Windows Server 2012 R2 as the OS.
- The PDC was set up with 12GB HDD, 512MB RAM, 1 vCPU.
- The SQL 2016 Servers were set up with 16GB HDD, 1GB RAM (recommended minimum), 1 vCPU.
- The PDC has AD, DNS and other bits installed so I can create an OU structure and apply GPOs.
- The SQL 2016 servers have the RTM Developer Edition installed (SQL 2016 Dev Edn is now free).
- My main aim is to test FCI and Availability Group setups from a SQL architectural point-of-view.
- I’ll test the new ‘Basic Availability Group’ that comes with SQL 2016 Standard Edition some other time.
- I can add more VMs as required (so I can scale my FCI and AG to conduct latency tests under load).
- Yes, my desktop needs another 8GB of RAM (or more) so I can increase my VM resources.
- I love MSDN as it allows me to build these test labs where I can explorer and mimic client issues when troubleshooting etc.
- I do like the more streamlined and feature-rich SQL 2016 SSMS (especially setting up multiple tempdb files during the install and enabling IFI).