tag:blogger.com,1999:blog-5485181488522668586.post6168027557057866146..comments2024-02-21T07:46:27.287-05:00Comments on SQLBalls: SQL 2014 SSMS is Killing my C:Bradley Ballhttp://www.blogger.com/profile/08229829101131724200noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5485181488522668586.post-11663016324006595502015-11-30T02:15:39.254-05:002015-11-30T02:15:39.254-05:00Rather than deleting the temp file. you can close ...Rather than deleting the temp file. you can close SSMS program and it will free C:\ drive space.Sanjaynoreply@blogger.comtag:blogger.com,1999:blog-5485181488522668586.post-14222832751047273552013-10-16T11:22:35.500-04:002013-10-16T11:22:35.500-04:00Hey Andrew, that's not a bad idea. Yeah I tho...Hey Andrew, that's not a bad idea. Yeah I thought I had a bug, and then found out it was by design. I ended up going in SSMS and saying discard results after execution. That way I could still execute the query, just no temp results to blow out my C drive.Bradley Ballhttps://www.blogger.com/profile/08229829101131724200noreply@blogger.comtag:blogger.com,1999:blog-5485181488522668586.post-30892191540697123502013-10-15T22:59:57.231-04:002013-10-15T22:59:57.231-04:00That would happen in any version of SSMS, the quer...That would happen in any version of SSMS, the query results need to be stored somewhere (would have thought RAM first but obviously not). <br /><br />According to this: <br /><a href="http://social.msdn.microsoft.com/Forums/sqlserver/en-US/fd63b3f2-0dbd-42a6-9706-91ae05754dab/management-studio-query-results?forum=sqltools" rel="nofollow">MSDN</a><br /><br />Resolution is to move your windows profile temp folder to a new location. <br /><br />It's fairly unusual to return GB's+ of results to the screen though. For the demo, what if you returned the results to a table variable (tempdb will grow instead).Anonymoushttps://www.blogger.com/profile/18333265840567558364noreply@blogger.com