|
|
Posted by Erland Sommarskog on 09/02/06 18:38
Jean-Marc Blaise (nobody@nowhere.com) writes:
> The trick to change the registry value of ProgramFilesDir cannot work
> because it breaks Outlook Express. In fact in the registries, you find
> hard coded Program Files for programs as well as %ProgramFiles%. So I
> used some tool to repartition my disk ...
Sorry, I forgot to say that I know if it is supported to change
ProgramFilesDir. When I have tried this for SQL 2005 installations, it
has been virtual machines with very little on.
Still, I'm surprised that it would break Outlook Express. My hinch
is that ProgramFilesDir mainly serves as a default for new installations.
Once something has been installed, it should not be affected by
a change in ProgramFilesDir. But I am not in expert on Windows, so I
could be wrong on that point. (And I'm too coward to try the experiment
on my real machine. :-)
> I find the setup pretty uncomprehensible, you don't know exactly despite
> the Disk Cost how much you will install in the system drive, and the
> path you select. I encountered twice setup problems (abort or willing to
> report to microsoft)... Basically, it seems to me I installed about 800
> Mb on both drives, not selecting Analysis Services.
I have shoehorned in SQL 2005 on virtual machines with low disk space,
and I don't recall any major mismatch with Disk Cost. But it goes without
saying that if Disk Cost says that you will have one megabyte left, you
should do some cleanup just in case.
> Then, installing SP1 ... took me from the system drive about 1 Gb, but
> moreover that annoys me is the time it takes to apply SP1: about 45
> minutes. I am very surprised and disappointed about all these
> disagrements, and I find even Oracle has made much progress on there
> installation gui (using Oracle 10gR2).
Yes, the SP1 takes up too much space on the system disk. It saves a lot
of install packages, but most packages are saved twice. Add to that a
PatchCache. Some of this stuff has to do with roiling back a service
pack, but you cannot roll back SP1.
I have a feeling that the SP1 setup was a bit rashed, because they
wanted to get Database Mirroring out of the door. There are a couple
bugs filed on the SP1 setup (including more than one from yours truly),
and I think several have been resolved as "looking into fix for SP2".
In any case, it is quite clear that if you are of the school that
the system drive should be small, you should re-think, because that is
not Microsoft's approach, but it appears they will continute to cram
things into Windows/Installer, and force thing into ProgramFilesDir.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|