By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,921 Members | 1,479 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,921 IT Pros & Developers. It's quick & easy.

MSSQL2K5 Install Path

P: n/a
Hi,

How can I make MSSQL2K5 setup install everything in the install path I have
choosen - it keeps installing some files in ¨%SystemRoot% ?

Thanks,

JM
Aug 28 '06 #1
Share this Question
Share on Google+
6 Replies


P: n/a
Jean-Marc Blaise (no****@nowhere.com) writes:
How can I make MSSQL2K5 setup install everything in the install path I
have choosen - it keeps installing some files in ¨%SystemRoot% ?
If you just choose an alternate location at installation time, it's only
a minor part of the files that are relocated. Something like 1.6 GB ends
up on the system disk if you install everything.

If you change the registry value
HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/ProgramFilesDir
you can force quite a lot to a second disk.

You still get some files in %SystemRoot%. As I recall, the main bulk of
this ends up in the Installer directory. I think you can change some
registry setting to have the Installer directory elsewhere, but I would
recommend that you think twice before you make this step. On a new
machine it may be less of an issue, but if you already have stuff there,
you may mess up other programs.

SP1 takes an even heavier toll on the Installer directory.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Aug 28 '06 #2

P: n/a
Hi Erland,

I will try to relocate ProgramFilesDir registry to install MSSQL2K5.

Great thanks for your explanations,

JM

"Erland Sommarskog" <es****@sommarskog.sea écrit dans le message de
news:Xn**********************@127.0.0.1...
Jean-Marc Blaise (no****@nowhere.com) writes:
How can I make MSSQL2K5 setup install everything in the install path I
have choosen - it keeps installing some files in ¨%SystemRoot% ?

If you just choose an alternate location at installation time, it's only
a minor part of the files that are relocated. Something like 1.6 GB ends
up on the system disk if you install everything.

If you change the registry value
HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/ProgramFilesDir
you can force quite a lot to a second disk.

You still get some files in %SystemRoot%. As I recall, the main bulk of
this ends up in the Installer directory. I think you can change some
registry setting to have the Installer directory elsewhere, but I would
recommend that you think twice before you make this step. On a new
machine it may be less of an issue, but if you already have stuff there,
you may mess up other programs.

SP1 takes an even heavier toll on the Installer directory.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Aug 29 '06 #3

P: n/a
Hi Erland,

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 ...

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.

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).

Do you have any comments on my feelings ?

Regards,

Jean-Marc

"Erland Sommarskog" <es****@sommarskog.sea écrit dans le message de
news:Xn**********************@127.0.0.1...
Jean-Marc Blaise (no****@nowhere.com) writes:
How can I make MSSQL2K5 setup install everything in the install path I
have choosen - it keeps installing some files in ¨%SystemRoot% ?

If you just choose an alternate location at installation time, it's only
a minor part of the files that are relocated. Something like 1.6 GB ends
up on the system disk if you install everything.

If you change the registry value
HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/ProgramFilesDir
you can force quite a lot to a second disk.

You still get some files in %SystemRoot%. As I recall, the main bulk of
this ends up in the Installer directory. I think you can change some
registry setting to have the Installer directory elsewhere, but I would
recommend that you think twice before you make this step. On a new
machine it may be less of an issue, but if you already have stuff there,
you may mess up other programs.

SP1 takes an even heavier toll on the Installer directory.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Sep 2 '06 #4

P: n/a
Jean-Marc Blaise (no****@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, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Sep 2 '06 #5

P: n/a
Hi Erland,

No problem for the ProgramFilesDir, I just keep posted so that people are
aware of some side effects :-).

Regarding the disk cost, it's confusing, let me tell why: you choose for
example Client Components / and the first sub choice. This gives you about
47 Mb. Then, going to Disk Cost, it says: 467 Mb ! Yeah, about 10 times. I
figure out that this is linked to the temporary files, msi file saved ...
And when you install only this, it seems to install many things: Workstation
Components for instance (at least it sets up some things related to this
area); the setup even tells "Removing applications", and you see your disk
storage decrease...

I know that the installer has some habit to copy twice (sometimes 3 times)
the package: I experimented one time the impossibility to remove anything
from my computer and had to play with registries to get back control of my C
drive. In not so old times, 5 Gb were fine on C: drive, now you should use
at least 20 gb to be safe. Unfortunately, on my labtop, I cannot reformat,
so am unable to install MSSQL2K5, and keep the old MSSQL2K.

Regards,

JM

"Erland Sommarskog" <es****@sommarskog.sea écrit dans le message de
news:Xn**********************@127.0.0.1...
Jean-Marc Blaise (no****@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, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Sep 4 '06 #6

P: n/a
Jean-Marc Blaise (no****@nowhere.com) writes:
Regarding the disk cost, it's confusing, let me tell why: you choose for
example Client Components / and the first sub choice. This gives you about
47 Mb. Then, going to Disk Cost, it says: 467 Mb ! Yeah, about 10 times. I
figure out that this is linked to the temporary files, msi file saved ...
Yeah, that part which says "this compoent requires xx MB on your hard
disk" is about useless. You have to go to Disk Cost to see the actual
effect.

I guess the basic problem is that the cost for a feature depends very
much on which other features you install. For instance, if I go to
Add/Remove Programs, it tells me that Microsoft Visual Studio Team
Suite for Database Professionals - ENU (a.k.a DataDude) takes up 799 MB.
Maybe that would be true, if DataDude was the only Visual Studio thing
I had installed, but it's just an add on, which I have installed
separately. (DataDude is a VS component that is still in beta.)
In not so old times, 5 Gb were fine on C: drive, now you should use
at least 20 gb to be safe. Unfortunately, on my labtop, I cannot reformat,
so am unable to install MSSQL2K5, and keep the old MSSQL2K.
If unpatitioned disk to spare, keep in mind that you can add a partition
as a mount point, so you could move for instance C:\Windows\Installer
out from the system disk.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Sep 4 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.