I agree with sodeep; it is created by system per instance and is advisable to have a separate drive for tempdb. Also, if tempdb is using it's max capacity, please restart the sql server to reclaim the disk space before it throws an error on tempdb full.
I agree with sodeep; it is created by system per instance and is advisable to have a separate drive for tempdb. Also, if tempdb is using it's max capacity, please restart the sql server to reclaim the disk space before it throws an error on tempdb full.
Thanks, Sri.
If you restart to reclaim tempDB space won't you take a bit of a performance hit while tempDB rebuilds itself? If its running close to its memory limit wouldn't it be better to resize tempDB via the alter database command?
Restarting SQL Server is the last option.It is better to plan for tempdb with space and have them in separate drive(ex: RAID 10) and split them based on processors. If many of the queries are using tempdb or Online Reindexing, you should find better alternative or tune the queries.