ffscout Posted December 9, 2013 Report post Posted December 9, 2013 Hi, Not sure if I should put this in the SQL forum but I'll start it off here. I have been running SCCM 2012 for a few month now and on occasion the SQLServer service seems to eat up all the disk space on the D drive, I have both SCCm and SQL installed on that disk, this was fine I could just restart the service and everything would be ok for a good while. However in the last week it is constantly using up all the disk space to the point I'm having to restart the service multiple time a day. Any advice on why this is happening would be great and any tips to resolve the issue would be even better. Thanks Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted December 9, 2013 Report post Posted December 9, 2013 where are your sql logs being stored, that could likely be a cause of your problems.. Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted December 9, 2013 Report post Posted December 9, 2013 And Where is your Temp db? Have you looked to see what exactly is eating up all the space? Quote Share this post Link to post Share on other sites More sharing options...
ffscout Posted December 9, 2013 Report post Posted December 9, 2013 I've checked the logs on the drive there and they are not that big having said that I never checked them until I restarted the service so I'll have to check that again next time it fills up. The Temp db is on the same drive, would it be a good idea to set it to auto shrink or will this have an impact on performance? Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted December 9, 2013 Report post Posted December 9, 2013 If the problem is the temp db, then issue is likely that someone is running a poorly written query that is filling it up. You can fix it bad capping the temp DB size but that will make the query stop working too. Once you figure out what is filling up all the space you and work on how to fix it. Quote Share this post Link to post Share on other sites More sharing options...
ffscout Posted December 16, 2013 Report post Posted December 16, 2013 Thanks for the advice on this, I think you have something with the poorly written query, I've ended up moving the tempdb to a seperate drive at the moment so I did not have to extend the current one and can move it back once I comb through these queries. Quote Share this post Link to post Share on other sites More sharing options...