Since SQL 2017 doesn't have any service packs, is there any difference in the process to apply CUs? How do we know how much free space on the drive is required to apply the cumulative updates on SQL Server RTM?
Thanks
How did you know the answer to your latter question for SPs? If it isn't included in the documentation for the CU, then you have to assume that you need the same amount of headroom as an initial installation. That can be found under "Disk space requirements" in the article for 2016/2017 at the following link:
--Jeff Moden
Change is inevitable... Change for the better is not.
May 8, 2022 at 12:02 am
If you have SSAS also installed with Database services on the server, do you need to apply cumulative updates separately or it will give you the option to select both database services & Analysis services at same time as installation!
May 8, 2022 at 10:02 pm
If you have SSAS also installed with Database services on the server, do you need to apply cumulative updates separately or it will give you the option to select both database services & Analysis services at same time as installation!
Heh.... I don't know. It's one of the 4 letter words that I don't install. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
May 10, 2022 at 5:25 am
This was removed by the editor as SPAM
May 12, 2022 at 5:45 pm
If you have SSAS also installed with Database services on the server, do you need to apply cumulative updates separately or it will give you the option to select both database services & Analysis services at same time as installation!
No. The CU will update all of the features you have installed. You can un-select features to update in the install of the CU, but you probably would not want to do that.
What kind of free space would you be expecting to require? CU29 (the latest) is about 500 MB in size.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
May 12, 2022 at 5:50 pm
No. The CU will update all of the features you have installed. You can un-select features to update in the install of the CU, but you probably would not want to do that.
To that very point, I made the egregious error of saying I don't install the various 4 letter words that SQL Server comes with. That's actually not true. I install EVERYTHING and then turn off the services that are not going to be used. Saves me a whole lot of aggravation when someone has something like an SSRS hot-flash. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2022 at 6:55 am
I will give a long answer and a short answer:
The long answer treats your servers like pets, you need to spend time caring for each of them. The amount of space needed for your program files will increase over time as you apply Windows and SQL fixes. A useful rule is allow 100 MB per month for Windows fixes plus a further 100 MB every 2 months for SQL fixes. If you copy the SQL CU to your server to install it then either delete it after the install has ended or allow 250MB every 2 months for the CU media.
If you put your SQL program files on a different volume to Windows then the growth allowance needs to be split across these volumes. However, some SQL program files will always live on the system volume.
Next, decide how many years you will keep your server. Multiply the growth allowance by the number of months needed and you have an idea of the total space needed.
The short answer is to treat your servers more like cattle and look to the needs of the herd. Put the SQL program files on the system volume and give it 120 GB storage. All modern storage subsystems allow for sparse provisioning of volumes so ensure this is enabled for the system volume. You may start with maybe 60% apparent free space on your system volume which gives ample allowance for many years of fixes, but only the space used is stored on storage. This way your storage manager only has to monitor total space actually used, and does not need to worry about server-level details.
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
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply