August 30, 2012 at 8:42 am
Hello everyone, I'm responsible in installing SQL Server 2008 R8 standard on a system running windows server 2003 SP2. Unfortunately that is a system that is in production running several apps during the day. During off hours I could do the install, that is the easy part. However, I only have about 2.75 GB on the C drive. I also have a D drive that I can use to install the mdf files and log files once SQL Server is install. My problem is that the setup process still requires me to have around 3GB of free space on the C hard drive. I cannot free any more space, believe me I already tried, I check logs to delete, temp files, and move documents to different locations. Is there any way around this? I specified in the install process to point to the D drive but the setup still requires more space which I don't have. Any suggestions and ideas would be very appreciated.
Thank you.
August 30, 2012 at 9:14 am
Increase disk space.
2.75 GB free on the system drive is not enough anyway to have decent performance.
-- Gianluca Sartori
August 30, 2012 at 9:33 am
I understand, we're working on a data conversion (oracle to sql) once the conversion on completed, the oracle data would be deleted and will free up some space. I'm hoping to work around this without having to replace my hardware now.
August 30, 2012 at 9:38 am
You mean you have Oracle data on the system drive?
Doesn't look like a great idea...
-- Gianluca Sartori
August 30, 2012 at 9:44 am
The whole system setup from the beginning was not a great idea (12 GB for the C drive, most of it is in the windows directory and the bak files for oracle). The system is running an oracle database on the d drive which has plenty of space and running backup to the c drive. That is not my best scenerio either. If I could I would repartition and start from from zero. It seems that I'm stuck until I get a new system that can handle the right space requirements.
August 30, 2012 at 9:50 am
You maybe could trick the installer mounting a disk as a folder in the C drive.
You just have to find where the installer looks for free space and tries to write its data.
Don't know if that would work though.
-- Gianluca Sartori
August 30, 2012 at 10:03 am
What about using a tool like the GParted Live CD to actually resize the partitions? I would prefer to do this without any data on the D: drive but as long as you're not making it so much smaller as to not have enough room for the data on it you should be fine. I'd grow C: to at least 20 or 30 if not more.
Editted to add the link.
August 30, 2012 at 10:18 am
Well, if the system partition is part of a bigger disk shared with the data partition, gparted could be an option.
Take into account that if you enlarge a partition taking space from another one, you have to move the second partition's offset accordingly and that can take ages.
-- Gianluca Sartori
August 30, 2012 at 11:17 am
That's true, I'm assuming both partitions are part of a larger logical volume like a RAID. If the storage is something else like a single physical disk for C: or they're both LUNs then Gparted isn't an option.
August 30, 2012 at 12:52 pm
I believe they are in a RAID, I'll check with my network guys. It seems that at the end the answer that I wanted to hear never came. We'll have to come up with a different solution, another box or a virtual machine. Thanks a bunch for your responses.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply