The TempDB tab on the SQL Server 2016 installer is a really nice addition to the install wizard (along with the tick box to enable Instant File Initialisation). I was interested to see if I could remove the manual step of setting the TempDB files to something sensible via a script after the install.
This new tab lets you choose the number of files, their initial size and their auto growth size. You can spread files over multiple drives and configure the log file separately. One thing I found disappointing, was that the defaults are still really bad. With that said Number of Files has a default of 4 which is nice. So, like most people, I altered these default settings to better suit my requirements.
Ah red is not good. I’ve configured my TempDB files in what seem like a fairly reasonable way but the installer is not happy.
The messages are as follows:
The value XXX for the TempDB file size exceeds the allowed limit. Setup allows the value up to 256MB because of the impact to installation time. You can set it to a higher size after the installation.
The value XXX for the TempDB file growth exceeds the allowed limit. Setup allows the value up to 256MB. You can set it to a higher size after the installation.
I tried lowering the file count to see if the limit was spread across the files but no joy.
256MB seems like such a small amount. Will it really impact installation time to 0 out a 1GB file (especially as I enabled IFI in a previous step in the install)? I think this will mean a lot of people will ignore this tab and stick to their post install scripts to configure TempDB.
This is still the Community Technology Preview of 2016 so it might still change (again).