There are some long running queries that are using all of the available disk space (yeilding an error: log file for temdb is full). I wanted to point temmplog.ldf to a larger disk (it only has 5GB available on the current disk), but our dba insists that it would be better to disable tempdb for these queries.
SQL uses tempDB for many reasons. I've never seen any way to "disable" its use. I've never known a reason to do so.
You can mitigate the problem by using permanent tables rather than temporary tables where the temp tables are explicitly created. Of course, this would just increase the size of another data and log file and you could have the same problem.
Are the large queries select or updates? Have the queries been optimized to reduce the required resources? Terry L. Broadbent - DBA
Computing Links:
Thanks, Terry. I agree completely. The queries are just selects, but not all of the joined fields are indexed. I'm sure that has a significant impact. Considering that the purpose of the queries is to validate data in a new table (they won't likely be used again), I didn't want to invest the time and disk space to indexing all of these fields. My guess is that since there is only 5gb available for the current log file, perfomance enhancements wouldn't be enough.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.