Folks,

I have a server with 2 volumes: C and D. I do not have enough disk space to
install SQL2K5 due to insufficient disk space on the C drive. Even though I
specifically state during the install to not install anything on the C drive,
it still wants to. I go through each and every feature selection and change
the installation path, but to no avail. it seems to need the C drive.

So my question is this, is it possible to instruct SQL2K5 install to not put
anything on the C drive? Perhaps a registry setting?

--
Thanks,

Scott H.

You have very limited control over where SQL will put its executable files.
The system volume footprint of SQL Server is only controlable within certain
limits. A lot of the components are going to go on C: and you really cannot
chnage that. I would image your system and repartition the drives to
enlarge C:

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Scott H." <ScottH@discussions.microsoft.com> wrote in message
newsD12DEFB-8A17-49E5-AFCF-82152146D7E4@microsoft.com...
> Folks,
>
> I have a server with 2 volumes: C and D. I do not have enough disk space
> to
> install SQL2K5 due to insufficient disk space on the C drive. Even though
> I
> specifically state during the install to not install anything on the C
> drive,
> it still wants to. I go through each and every feature selection and
> change
> the installation path, but to no avail. it seems to need the C drive.
>
> So my question is this, is it possible to instruct SQL2K5 install to not
> put
> anything on the C drive? Perhaps a registry setting?
>
> --
> Thanks,
>
> Scott H.

Thanks Geoff. I was able to squeeze enough space.

It is interesting to note that upon selection, when I checked associated
disk cost, I was left with ~39MB of available disk space on the C volume.
Once the installation was complete available disk space on C went to ~600MB.
Seems that the installation requires some temporary disk space also.
--
Thanks,

Scott H.


"Geoff N. Hiten" wrote:

> You have very limited control over where SQL will put its executable files.
> The system volume footprint of SQL Server is only controlable within certain
> limits. A lot of the components are going to go on C: and you really cannot
> chnage that. I would image your system and repartition the drives to
> enlarge C:
>
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
>
>
> "Scott H." <ScottH@discussions.microsoft.com> wrote in message
> newsD12DEFB-8A17-49E5-AFCF-82152146D7E4@microsoft.com...
> > Folks,
> >
> > I have a server with 2 volumes: C and D. I do not have enough disk space
> > to
> > install SQL2K5 due to insufficient disk space on the C drive. Even though
> > I
> > specifically state during the install to not install anything on the C
> > drive,
> > it still wants to. I go through each and every feature selection and
> > change
> > the installation path, but to no avail. it seems to need the C drive.
> >
> > So my question is this, is it possible to instruct SQL2K5 install to not
> > put
> > anything on the C drive? Perhaps a registry setting?
> >
> > --
> > Thanks,
> >
> > Scott H.
>
>

Yes, most installations require a significant amount of additional free
space to support the install.

There is also a pretty substantial set of logs written to the Windows folder
somewhere, which you could probably either move to an alternative drive or
delete altogether in order to reclaim a bit of the space.

All that said, there is no reason anymore to have a small C:\ drive, and
plenty of reasons to make it larger than the typical 4GB or 8GB (I don't
even think you can install current versions of Windows in that space,
without adding any applications or services). Which wouldn't have solved
the immediate problem (unless you could re-image or rebuild), but should
guide you in configuring your next system.




On 5/15/08 7:57 AM, in article
637B7908-0108-4FAE-A771-FE0D1863E9BA@microsoft.com, "Scott H."
<ScottH@discussions.microsoft.com> wrote:

> Thanks Geoff. I was able to squeeze enough space.
>
> It is interesting to note that upon selection, when I checked associated
> disk cost, I was left with ~39MB of available disk space on the C volume.
> Once the installation was complete available disk space on C went to ~600MB.
> Seems that the installation requires some temporary disk space also.