December 27, 2007 at 8:31 am
Hello,
I have 2 physical drives that are mirrored. There is a C: and D: drive, annoyingly the C: with only server 2003 has 6GB free left on it, the D: is 123 GBs.
Now I am going to put to SQL on the D: (the logs and DB's will be located on a connected SAN) but as I have loaded SQL at home, I find it tends to fill up the C drive with Temp files in a SQL shared folder when you want to add or change something to your installation even if you load SQL onto the D:. Does anybody know if I can prevent this from happeing on the C and on the D drive instead?
Regards,
D.
December 27, 2007 at 8:41 am
you can't prevent creation of temp files.
you can install all of sql on D and that should be fine as long as you create logs and data files on the SAN.
December 27, 2007 at 9:04 am
This is one of the very annoying things about SQL Server. There are times, especially with the Service Packs, that it wants to put some stuff on C for the installation. It should be temporary and if you can move the Pagefile to D and delete some Windows temporary files, you should be ok.
As Alex mentioned, put other stuff on the SAN or D for SQL Server itself.
December 28, 2007 at 9:20 am
Try changing the Temp and Tmp environment variables to something like D:\Temp. You could also try creating a local policy that moves user folders to the D: drive. That way when you are doing the install or SPs the temp files are all redirected to D:.
December 28, 2007 at 1:40 pm
Hi,
As pointed out if your Environmental Variables for the OS are set to an alternate location you can avoid the temp file issue.
I just had this at a client - worse over, some pillock made their C drive 4GB.... Didn't that end with NT 4.0 🙂
Cheers
Ian
December 31, 2007 at 2:57 am
Hello,
Thanks for your replies, in the end I had to reinstall the system anyway, because I decided to put VMware on it and it didnt have enough space to install itself. But I will try your suggestions on the virtual machines.
Regards,
D.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply