You have a Microsoft SQL Server 2014 named SRV2014 that has a single tempdb database file. The tempdb
database file is eight gigabytes (GB) in size.
You install a SQL Server 2016 instance named SQL Server 2016 by using default settings. The new instance
has eight logical processor cores.
You plan to migrate the databases from SRV2014 to SRV2016.
You need to configure the tempdb database on SRV2016. The solution must minimize the number of future
tempdb autogrowth events.
What should you do?
A.
Increase the size of the tempdb data file to 8 GB. In the tempdb database, set the value of the MAXDOP
property to 8.
B.
Increase the size of the tempdb data files to 1 GB.
C.
Add seven additional tempdb data files. In the tempdb database, set the value of the MAXDOP property to
8.
D.
Set the value for the autogrowth setting for the tempdb data file to 128 megabytes (MB). Add seven
additional tempdb data files and set the autogrowth value to 128 MB.
Explanation:
In an effort to simplify the tempdb configuration experience, SQL Server 2016 setup has been extended to
configure various properties for tempdb for multi-processor environments.
1. A new tab dedicated to tempdb has been added to the Database Engine Configuration step of setup
workflow.
2. Configuration options:
Data Files
* Number of files – this will default to the lower value of 8 or number of logical cores as detected by setup.
* Initial size – is specified in MB and applies to each tempdb data file. This makes it easier to configure all files
of same size. Total initial size is the cumulative tempdb data file size (Number of files * Initial Size) that will be
created.
* Autogrowth – is specified in MB (fixed growth is preferred as opposed to a non-linear percentage based
growth) and applies to each file. The default value of 64MB was chosen to cover one PFS interval.
Figure:
https://blogs.msdn.microsoft.com/psssql/2016/03/17/sql-2016-it-just-runs-faster-automatictempdb-configuration/
