0

We're currently using the tempdb to manage our SQL session state, but its size keeps growing out of control. Is there any way to manage or prevent this from happening?

We are thinking of setting up a custom database to manage SQL state instead of the tempdb, is this going to solve the problem?

Also, is there anything that we should be aware of when setting up and switching to a custom database?

Thanks.

Martyn
  • 1,446
  • 2
  • 19
  • 30
  • I struggle to think why using TempDB for session state would be a good idea. A dedicated database is the *normal* way. – Richard Mar 17 '11 at 10:47

1 Answers1

2

Make sure that the SQL Server Agent is running. This is required to do clean up of the temp tables.

http://support.microsoft.com/kb/317604

lrixford
  • 36
  • 2