SQL Server 2016 Release Candidate 0 is out. Here’s what the installation process looks like:
Note that on the Installation tab, though, there’s a new line for “Install SQL Server Management Tools.”
This is the continuation of last year’s separate SQL Server Management Studio installation process, with its own check-for-updates process separate from SQL Server’s servicing.
For years, some admins have insisted that the management tools should never be installed on the SQL Server itself, and that it should only be administered remotely. I don’t really have a dachshund in that race, but before you get too excited, note that SSMS wasn’t installed by default to begin with. If somebody wanted to check that box, they’ll also be willing to run a separate setup to get SSMS on the server.
I’m going to skip a few screens that haven’t changed, but here’s the new list of features:
Note, Management Studio is gone, with Advanced Analytics and PolyBase Query Service showing up.
One thing that still hasn’t changed, in the fine prerequisite print on the right side: you still have to manually install the .NET Framework v3.5. Database admins have been complaining about this for years. The installer still fails if you don’t manually install this first.
After fixing that and passing setup validation, there’s a new checkbox for enabling Instant File Initialization:
This just grants the necessary permissions to the account you picked during setup. It’s not on by default, which is probably a safe security decision.
Next up is TempDB – and note how I capitalized that, dear reader:
Forget the file configuration – the big news here is that Microsoft agrees with me: when discussing the public toilet, it needs a capital T for TempDB.
Also news but not nearly as cool, Microsoft automatically adds more TempDB files by default – the 4 file quantity was picked automatically for me here, as were the 8MB file sizes and 64MB autogrowth increments.
Because I work with data larger than a single digital camera picture, I upsized my files, but you can only go so far:
You can put up to 1GB for the data and log file sizes – if you try anything higher, the GUI just silently revises your numbers back down to 1GB. Interestingly, if you hit Next, even a 1GB log file isn’t allowed:
Carrying on – after installation finishes, here’s what your start menu looks like:
Yes, 2008. Whatever. Next up, let’s use the management tools installer. While the engine’s installer has grown more complex, the management installer goes in the exact opposite direction:
No options – you’re just either in, or you’re out. During installation, the part that takes the longest time by far is the VS 2010 installation:
And we’re done! Off to play with the new features.