NO SQL Server components should be installed on OS drive (C drive)

Question

Post reply

NO SQL Server components should be installed on OS drive (C drive)

gary1

SSC-Insane

Points: 21152
More actions
March 7, 2012 at 10:14 am

#258139

Hi,
Our new policy is NOT to install any SQL Server components on OS drive.
While installing SQL Server 2008 R2 through installation Wizard, I did not select C (OS) drive any where.
But after the installation, I noticed the following folder got created on OS (C) drive.
1. C:\Program Files\Microsoft SQL Server\80\COM\sqlvdi.dll
2. C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlvdi.dll
3. C:\Program Files\Microsoft SQL Server\90\License Terms\1033\license_SQLWriter.txt
4. C:\Program Files\Microsoft SQL Server\100 (Under this path there few folders like COM, KeyFile, License Terms, Setup Bootstrap, Shared)
5. C:\Program Files\Microsoft Analysis Services\AS OLEDB\10 (sevaral files under the folder 10.)
What are the steps to follow so that NO SQL Server components should be installed on OS drive (C drive)?
Thanks

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 1

There are none, I don't believe you can do it. Sorry mate..

CEWII

Lowell SSC Guru Points: 323518 More actions · Answer 2

Agreeing with Elliot here;

i've seen numerous posts here requesitng the same thing.

AFAIK the biniaries that are the core service and stuff must be installed on the %systemdrive%, with no choice in the matter...you can move the databases, i thought, but the binaries go on that drive(C: on most of my machines)

Of course the client tools can be installed/re-installed elsewhere, but

I am sure of the service binaries requiring %systemdrive%

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Jared SSC Guru Points: 61793 More actions · Answer 3

Agreeing with the others... You can choose where the shared components, data files, logs, and backups go. After that, it will put everything where it needs to be. Sounds like whoever made this decision didn't know what they were deciding; i.e. to follow that rule you will not have SQL Server installed.

Jared
CE - Microsoft

SQLRNNR SSC Guru Points: 281334 More actions · Answer 4

Echo

Some of the SQL binaries and components must be installed on the system drive. You can redirect some of the program install, but not all of it. I wouldn't try changing it either.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

spaghettidba SSC Guru Points: 105732 More actions · Answer 5

You could move those files to a non-system drive and create a junction on the system drive.

That way, the files would appear on both drives, but will physically reside outside the OS drive.

-- Gianluca Sartori

Eugene Elutin SSC Guru Points: 59322 More actions · Answer 6

:

_____________________________________________
"The only true wisdom is in knowing you know nothing"
"O skol'ko nam otkrytiy chudnyh prevnosit microsofta duh!":-D
(So many miracle inventions provided by MS to us...)

How to post your question to get the best and quick help[/url]

Eugene Elutin SSC Guru Points: 59322 More actions · Answer 7

Gianluca Sartori (3/8/2012)
You could move those files to a non-system drive and create a junction on the system drive.
That way, the files would appear on both drives, but will physically reside outside the OS drive.

Have you ever tried to do it?

_____________________________________________
"The only true wisdom is in knowing you know nothing"
"O skol'ko nam otkrytiy chudnyh prevnosit microsofta duh!":-D
(So many miracle inventions provided by MS to us...)

How to post your question to get the best and quick help[/url]

spaghettidba SSC Guru Points: 105732 More actions · Answer 8

Yes, and it worked.

I also tried many other horrible things with junctions, but that would be a whole different story. 😀

-- Gianluca Sartori

Eugene Elutin SSC Guru Points: 59322 More actions · Answer 9

Gianluca Sartori (3/8/2012)
Yes, and it worked.
I also tried many other horrible things with junctions, but that would be a whole different story. 😀

It's nightmare for free...

_____________________________________________
"The only true wisdom is in knowing you know nothing"
"O skol'ko nam otkrytiy chudnyh prevnosit microsofta duh!":-D
(So many miracle inventions provided by MS to us...)

How to post your question to get the best and quick help[/url]

spaghettidba SSC Guru Points: 105732 More actions · Answer 10

Well, not really. It's just something we're not used to see in Windows, but it's a totally normal thing in *nix.

In Win2008 and Win7 folders appear with the link overlay and in command windows they appear as <JUNCTION>.

The real nightmare was in Win2003 and WinXP that had no clue what a junction was. The dangerous thing is that deleting a junction deletes the junction destination, so that you may delete the only instance of a file thinking that it's a different copy. :sick:

-- Gianluca Sartori

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 11

Gianluca Sartori (3/8/2012)
Yes, and it worked.
I also tried many other horrible things with junctions, but that would be a whole different story. 😀

I think this falls into the category of can do it but shouldn't.

CEWII