January 16, 2018 at 11:23 am
Eric M Russell - Tuesday, January 16, 2018 10:30 AMI use tool on my personal PC to keep tabs on disk space allocation by folder. It would help in your case too.
https://jam-software.com/treesize_free/
Looks good. Too bad it doesn't have a CLI (Command Line Interface).
--Jeff Moden
Change is inevitable... Change for the better is not.
January 16, 2018 at 11:50 am
Eric M Russell - Tuesday, January 16, 2018 10:30 AMI use tool on my personal PC to keep tabs on disk space allocation by folder. It would help in your case too.
https://jam-software.com/treesize_free/
This is cool however I'd be fired for installing outside non-approved software on a corp server
January 17, 2018 at 8:06 am
It won't help your current problem, but you need to get your company rules changed for system drive size. 60GB for Windows and SQL server over a lifetime of 5 years is too small.
You need to factor in the size of Windows fixes (often over 500MB per month) and SQL fixes (often over 500MB every 2 months) which adds up to over 9GB increase in space used each year. Then add in Windows monitoring and log files and anything else that needs to live on the system drive and 60GB for the life of the server looks more like hope rather than reality.
FWIW we have a standard of 100GB for any system drive, more if it can be justified. But all our servers are virtualised and use thin provisioning so actual SAN space used is less than 100GB * ServerCount. Also virtual drives can be grown if needed.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
January 17, 2018 at 8:53 am
EdVassie - Wednesday, January 17, 2018 8:06 AMIt won't help your current problem, but you need to get your company rules changed for system drive size. 60GB for Windows and SQL server over a lifetime of 5 years is too small.You need to factor in the size of Windows fixes (often over 500MB per month) and SQL fixes (often over 500MB every 2 months) which adds up to over 9GB increase in space used each year. Then add in Windows monitoring and log files and anything else that needs to live on the system drive and 60GB for the life of the server looks more like hope rather than reality.
FWIW we have a standard of 100GB for any system drive, more if it can be justified. But all our servers are virtualised and use thin provisioning so actual SAN space used is less than 100GB * ServerCount. Also virtual drives can be grown if needed.
I completely agree with you, if there were to be any change, migrate it all to a Virtual SQL Server, and then manage space on an as needed basis, starting off with their set template of system build out. Any many of the SQL Servers bare metal or otherwise, are around for many many years only getting larger, even though cubes and tables may routinely get retired
January 17, 2018 at 9:14 am
I added a post around a year ago regarding (in my case) a lack of free space on the OS drive of Dev SQL Servers. There were no SQL db files on there just a load of crap! :crazy:
"I did not find any result with extracting the files as the SP installer still uses the C:\ drive, however what I did find, (and in 15+ years of SQL Server, I was not aware of this) is that whenever a SQL SP, CU or hotfix is installed it copies the whole caboodle to a specific folder, in my case: 'C:\Microsoft SQL Server\110\Setup Bootstrap\UpdateCache\' - there was 5GB!! of hotfixes/SPs in here! Anyone else aware of this? Incidentally, when doing a search for large files to remove, this folder is not picked up by the search.
So, if you need some free space on the OS drive, try looking in here first, could save the hassle of looking for files to remove or trying to get the drive size increased."
qh
January 17, 2018 at 10:14 am
I've had the log files in c:\windows\logs\cbs grow to tens of GB on many of our servers, especially on 2012 and 2012R2. It is one more place to look and may give you a quick win. You can find posts online describing how to delete the files, but the key is to stop the "Windows Modules Installer" service first. These files are recreated by the OS as needed if it finds them missing.
January 17, 2018 at 10:14 am
quackhandle1975 - Wednesday, January 17, 2018 9:14 AMI added a post around a year ago regarding (in my case) a lack of free space on the OS drive of Dev SQL Servers. There were no SQL db files on there just a load of crap! :crazy:"I did not find any result with extracting the files as the SP installer still uses the C:\ drive, however what I did find, (and in 15+ years of SQL Server, I was not aware of this) is that whenever a SQL SP, CU or hotfix is installed it copies the whole caboodle to a specific folder, in my case: 'C:\Microsoft SQL Server\110\Setup Bootstrap\UpdateCache\' - there was 5GB!! of hotfixes/SPs in here! Anyone else aware of this? Incidentally, when doing a search for large files to remove, this folder is not picked up by the search.
So, if you need some free space on the OS drive, try looking in here first, could save the hassle of looking for files to remove or trying to get the drive size increased."qh
I'll go out on a limb and ask,was it a safe delete with the file explore? I've deleted things in the past that way, only to find an unstable system
January 19, 2018 at 4:11 am
quinn.jay - Wednesday, January 17, 2018 10:14 AMquackhandle1975 - Wednesday, January 17, 2018 9:14 AMI added a post around a year ago regarding (in my case) a lack of free space on the OS drive of Dev SQL Servers. There were no SQL db files on there just a load of crap! :crazy:"I did not find any result with extracting the files as the SP installer still uses the C:\ drive, however what I did find, (and in 15+ years of SQL Server, I was not aware of this) is that whenever a SQL SP, CU or hotfix is installed it copies the whole caboodle to a specific folder, in my case: 'C:\Microsoft SQL Server\110\Setup Bootstrap\UpdateCache\' - there was 5GB!! of hotfixes/SPs in here! Anyone else aware of this? Incidentally, when doing a search for large files to remove, this folder is not picked up by the search.
So, if you need some free space on the OS drive, try looking in here first, could save the hassle of looking for files to remove or trying to get the drive size increased."qh
I'll go out on a limb and ask,was it a safe delete with the file explore? I've deleted things in the past that way, only to find an unstable system
As with most things we tested this on Development server first (and most of these spaces issues were on Dev boxes) and it worked fine.
For the odd Prod box where we had this issue, we moved the files to another drive rather than delete them. Again there were no issues. YMMV. 😉
qh
January 19, 2018 at 4:51 am
Jeff Moden - Tuesday, January 16, 2018 11:23 AMEric M Russell - Tuesday, January 16, 2018 10:30 AMI use tool on my personal PC to keep tabs on disk space allocation by folder. It would help in your case too.
https://jam-software.com/treesize_free/Looks good. Too bad it doesn't have a CLI (Command Line Interface).
😀 spot the cmd line junkie
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 19, 2018 at 7:22 am
Perry Whittle - Friday, January 19, 2018 4:51 AMJeff Moden - Tuesday, January 16, 2018 11:23 AMEric M Russell - Tuesday, January 16, 2018 10:30 AMI use tool on my personal PC to keep tabs on disk space allocation by folder. It would help in your case too.
https://jam-software.com/treesize_free/Looks good. Too bad it doesn't have a CLI (Command Line Interface).
😀 spot the cmd line junkie
Heh... guilty as charged. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 10 posts - 31 through 39 (of 39 total)
You must be logged in to reply to this topic. Login to reply