our SQL data base on server ASVS23432 that is affecting production. The tempdb is constantly eating up all the space left on the server and needs to be shrunk. Other databases seem to be holding onto unused space and leaving the server with minimal free space. Solution the server or the databases for better/correct performance.
If TempDB is growing very large then it is needed for the workload that is occurring. You will have to examine what is consuming the TempDB in order to pinpoint is it internal object or user objects. Shrinking TempDB is documented that it 'can' cause corruption. If other databases have free space in them as well that is due to them growing and possibly having a autogrowth size or percentage that is not optimal. There is no harm in data files having free space, it is actually recommended. When a data or log file grows transactions are suspended until the growth has completed. Excessive auto growing leads to performance issues.
Many question need to be answered first to fish out the source of your tempdb growth. Constantly growing....as in a huge burst of growth or slow growth on a daily basis? Those two conditions bring up a slew of other questions based on those scenarios. Are you using a ton of temporary tables in your stored procedures( if you have any, such as for ETL processes) that are maybe erroring out? If you are getting hang ups there or if your queries are taking forever to complete due to large amounts of inserts or deletes that could be one scenario of many, many more. Have you recently added a large publications and pushed out a huge data insert from replication? Do you have a transaction that is uncommitted and spinning somewhere in the background but not caught by anyone? Sorry but too many variables to offer up a good solution. You'll really need to jump on a profiler trace to really fish out what is causing your tempDB growth. I agree with Grant and Tim, Once you fish out your processes that will really help you.