June 14, 2013 at 8:03 pm
Hi,
I would like to know if it's possible to install SQL Server binaries on SAN drives (as we only have 1 local drive reserved for the OS).
Thank you,
Kukah
June 15, 2013 at 12:11 pm
By binaries do you mean the shared components (mangement studio, etc),or the SQL Server executables (SQLMAINT.EXE, SQLSVER.EXE)?
Shared components, if you want them, need to be installed in each node of the cluster separately.
The SQL Server executbles are installed on system drive (normally C) by the install program when you choose a cluster setup but the master/msdb database are installed on the shared storage that can be failed over. For 2008, you will need to run setup on each node and choose cluster setup.
June 15, 2013 at 9:48 pm
By binaries, I mean all executables of SQL / Instances / Features.
I've just end the demo.
When installing 1st Instance, even if I select another drive for the shared features directory and the Instance root directory, 1/2 of the installation files (in GB) goes to C:/system drive (around 3GB for full install/select all).
When installing a 2nd instance also full but w/out the shared components allready installed, 1/3 of the installation files goes to C:system drive, but only around 700 mb this time (and 17 mb for Shared components + 1,5GB for Instances files).
And so on for additional Instances.
Is there a way of install all the files in another partition ?
And I am effectively talking of a Cluster installation. Good guess ! :smooooth:
June 17, 2013 at 3:33 am
The SQL Server install process will always put about 3GB of files on to the System drive. Most of this is .Net routines that must be stored in the GAC which in turn must exist on the sytem drive. The SQL install process also needs about 2GB free space on the system drive while it runs, on top of what gets placed there permanently.
When you install service packs you should plan to add another 0.5GB to the system drive for each SP. A CU can also add a significant amount to system drive use. We have a standard of a 60GB system drive for any SQL Server machine, to allow enough space for patching over the expected lifetime of the box. We also boot direct to the SAN and do not use any server local drives, but that is just our preference.
The most that you can get to install elsewhere adds up to about 0.5GB. Service Packs hardly add anything to a non-system drive that has SQL binaries. My advise is to install all SQL binaries on the system drive, as this saves you a drive letter that can not be used for much.
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 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply