Managing the TempDB in order to improve performance
Article ID: 181562
Updated On:
Products
Issue/Introduction
The NS uses the TempDB quite intensively, and not just for temporary table creation, but also for temporary placement of data before it is processed. How can the TempDB be managed in such a way as to obtain good performance from it?
The following error may be seen in the Notification Server database:
Description: Security context setup failed:
The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION'.
Environment
ITMS 8.x
Resolution
Monitor the TempDB for a week, and then create two files that are 75% of the maximum size it reached over that week.
Shrinking the tempdb is a bad idea, as you end up fragmenting the physical file all over the disk. It is better to allocate the file(s) once with sufficient space to grow.
The following article provides some detailed information about how to optimise the TempDB:
Feedback
