I have a server (w2k, sp4) on which I have installed SQL w2k, sp3a.
It has two physical drives, C: (6gb) and D: (9gb). During the
install, I wanted to place the data files on the second drive. (I
know the executables and the system files go on the system drive.) I
know I can locate the data files elsewhere, as I've done it before.
(Although it's been a few years.) But during the install, when I
tried to place the data files on the second drive, the installer would
come back with 0 (zero) free space on the second drive, when in fact
all 9gb are unused. So I eventually settled on placing them on the
system drive. But I *really* want them on the second drive.
Might anyone have any idea as to what I did wrong? And/or what I do
now to move my data file location to the second drive? (Un-install &
re-install SQL Server?) I currently have none of my data in SQL. I'd
like to get this straightened out before I start building my files.
Thanks in advance,
Tom
Keith Kratochvil - 26 Apr 2005 19:37 GMT
I would leave the default databases where they are. When you create the new
databases just create them on the appropriate drive.

Signature
Keith
>I have a server (w2k, sp4) on which I have installed SQL w2k, sp3a.
> It has two physical drives, C: (6gb) and D: (9gb). During the
[quoted text clipped - 15 lines]
>
> Tom
Tom - 27 Apr 2005 00:19 GMT
Any idea why the installer said that there was zero space available on
the second drive?
>I would leave the default databases where they are. When you create the new
>databases just create them on the appropriate drive.
Keith Kratochvil - 27 Apr 2005 12:32 GMT
No, I have no idea. I have not experienced that issue before.

Signature
Keith
> Any idea why the installer said that there was zero space available on
> the second drive?
>
>>I would leave the default databases where they are. When you create the
>>new
>>databases just create them on the appropriate drive.