• Jeff Moden (12/1/2016)


    There's no way in hell that I'd enable TF 1117. It doesn't just affect TempDB and I don't want the nearly 90 temporal files/filegroups for a 600GB table to be all the same size because it would waste a huge amount of disk space.

    For TempDB, I've setup 8 files (we have 32 processors), have set them all to an initial size of 2GB each with 500MB growth each (they've never grown) and the log file to 2GB and, of course, have TF 1118 in play.

    Thankfully this has been fixed in SQL 2016! Now tempdb ALWAYS has BOTH enabled. And for other databases they are moved to ALTER DATABASE settings.

    https://blogs.msdn.microsoft.com/psssql/2016/03/15/sql-2016-it-just-runs-faster-t1117-and-t1118-changes-for-tempdb-and-user-databases/

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service