Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Full installation to a drive other than C: Expand / Collapse
Author
Message
Posted Thursday, May 22, 2008 8:36 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, November 19, 2013 7:04 AM
Points: 72, Visits: 172
Working with a customer who installed SQL 2005 onto drive C: but it is running out of space. (not much to start with). Now they have put in a new drive D: and wanted to uninstall SQL 2005 and install it to D:. Yes I know about selecting the option then selecting the advance to select the location of that feature. No matter what i set it to, it still wants to install some stuff to the C: is this just normal or is it possible to install ALL of it to D:?
Post #505215
Posted Thursday, May 22, 2008 10:43 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, August 10, 2010 5:07 AM
Points: 2,732, Visits: 23,078
When you do the initial install, if you go through the advanced installer, in one of the sub-sections of the installable products you will find that regardless of your initial choice it defaults some of the visual studio common tools to the C drive.

Once these tools are there, they cannot really be moved even though a SQL Server install can be moved.
Post #505324
Posted Monday, December 27, 2010 10:35 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:47 AM
Points: 6,306, Visits: 13,605
.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1039502
Posted Tuesday, January 4, 2011 5:37 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 4:14 AM
Points: 2,868, Visits: 3,215
The initial install of SQL Server 2005 will always put about 570 MB on the system drive.

Most of this goes into the Windows global assembly cache (GAC) which can only exist on the system drive. There is a further approx 430 MB that can be put on a different drive, meaning that the initial SQL 2005 install needs about 1GB of disk space, plus room for your databases.

A SQL 2005 service pack will add a further approx 800MB to the system drive, mainly due to GAC updates. Some CUs have been known to add a further 500 MB to the system drive. Items in the GAC very rarely get overwritten or deleted, so the GAC tends to grow quite large over time.

To minimise disk space for SQL 2005 components, go directly to SP4 and allow for space to accommodate your CU strategy.

The disk space requirements for other versions of SQL Server differ, with SQL 2008 needing about 3,000 MB on the system drive for the initial installation and 900 MB for a SP.


Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2014, 2012, 2008 R2, 2008 and 2005. 28 July 2014: now over 30,000 downloads.
Disclaimer: All information provided is a personal opinion that may not match reality.
Concept: "Pizza Apartheid" - the discrimination that separates those who earn enough in one day to buy a pizza if they want one, from those who can not.
Post #1042315
Posted Wednesday, January 5, 2011 7:02 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 11:57 AM
Points: 4,351, Visits: 6,166
As someone else said - installing SQL Server to a non-root drive still puts a LOT of crap in the root!! I would do one of two things: look for things you can delete from C to give you more size (all those blue windows update folders, temp directory crap, other install packages, etc). NOTE: removing some things can be problematic when other updates need to be installed!! I actually copy those folders elsewhere then I move them back if necessary later.

The other option is to get a tool like Paragon's partition manager to resize the boot partition if you are lucky enough that they didn't make it the full size of the disk and there is (or you can create) some free space.


Best,

Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #1043027
Posted Wednesday, January 5, 2011 8:41 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, November 19, 2013 7:04 AM
Points: 72, Visits: 172
Thank you all for the extra information. I had the client increase the size of the C drive/partition and got past the installation issue.
Again thanks...
Post #1043118
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse