Summary

This update improves the supportability of SQL Server 2012 and 2014 by adding informational messages for tempdb configuration to the SQL Server error log. After you install this update, an informational message that resembles the following is logged in the SQL Server error log at SQL Server startup:

The tempdb database has %ld data file(s).
Additionally, when there are multiple tempdb data files, if the tempdb data files do not have the same initial size or autogrowth size, an informational message that resembles the following is logged in the SQL Server error log:

The tempdb database data files are not configured to use the same initial size and autogrowth settings. To reduce potential allocation contention, the initial size and autogrowth of the files should be same.

More Information

The equal sizing of data files is important because the proportional fill algorithm is based on the size of the files. If data files are created with unequal sizes, the proportional fill algorithm tries to use the largest file more for GAM allocations instead of spreading the allocations between all the files. This defeats the purpose of creating multiple data files.

This update helps you check whether you are following the best practices recommendations in the Working with tempdb in SQL Server 2005 TechNet article.

This update is included in the following service packs for SQL Server:

       Service pack 3 for SQL Server 2014

       Service Pack 4 for SQL Server 2012

Service packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, together with any new fixes. Our recommendation is to apply the latest service pack and the latest cumulative update for that service pack. You do not have to install a previous service pack before you install the latest service pack. Use Table 1 in the following article for finding more information about the latest service pack and latest cumulative update.

How to determine the version, edition, and update level of SQL Server and its components

References

Recommendations to reduce allocation contention in SQL Server tempdb database

Concurrency enhancements for the tempdb database

SQL Server urban legends discussed

Compilation of SQL Server TempDB IO best practices

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×