![]() The time required to execute the largest batch in a database.The time required for the largest index maintenance operations.The time required to execute a full backup, because log backups cannot occur until it finishes.A good pointer to properly size a transaction log is monitoring the amount of log occupied during: The file growth increment on a log file should be sufficiently large to avoid frequent expansion. The automatic growth (autogrow) increment of the transaction log, as set by the FILEGROWTH option, must be large enough to stay ahead of the needs of the workload transactions. Recommendationsįollowing are some general recommendations when you are working with transaction log files: To control the maximum the size of a log file in KB, MB, GB, and TB units or to set growth to UNLIMITED, use the MAXSIZE option.įor more information, see the Recommendations in this topic.A value of 0 indicates that automatic growth is set to off and no additional space is permitted. To change the growth increment, use the FILEGROWTH option.To change the current file size in KB, MB, GB, and TB units, use the SIZE option. ![]() Use the ALTER DATABASE (Transact-SQL) File and Filegroup options statement to manage the growth of a transaction log file. For more information, see tempdb Database. You can avoid this overhead by increasing the size of the tempdb transaction log after starting or restarting the server instance. This can reduce the performance of the tempdb transaction log. Restarting a server instance resizes the transaction log of the tempdb database to its original, pre-autogrow size. For more information, see ALTER DATABASE (Transact-SQL) File and Filegroup options.įor more information, see the Recommendations in this topic.
0 Comments
Leave a Reply. |