Post reply

Cannot install SQL 2005 on the D drive.

  • June 21, 2011 at 4:26 am

    #145824

    Hello,

    I'd imagine that somebody would have come across this before, I am trying to install SQL 2005 R2 (downloaded from MSDN) to install in the D drive, I specify the D drive during setup but this appears not to work as the engine and everything else ends up on C, is there a work around for this? Its just ridiculous. I understand that SOME things end up on C, but I know the difference. Any advice is appreciated.

    Thank you for reading,

    D.

  • June 21, 2011 at 4:48 am

    #1341721

    whats the error you get when installing , is D drive a mapped network drive ? does it have enough space.

    Jayanth Kurup[/url]

  • June 21, 2011 at 5:12 am

    #1341732

    Hello, thank you for getting back.

    The D drive currently has lots of space, in fact its empty and bit enough. I do not get any errors, it all goes as normal but when installation is finished you can just see that the root directory is C and not D in the server properties and window explorer.

    Regards,

    D

  • June 21, 2011 at 5:41 am

    #1341754

    Correct me if I am wrong here , you are trying to install SQL on D drive ?

    By this I mean the problem is not about placing the mdf and ldf files for a database on the D drive.

    could you post the path where sql is installed?

    Also could u try creating a database and get back about where it was created.

    Jayanth Kurup[/url]

  • June 21, 2011 at 5:47 am

    #1341760

    Hello,

    Yes I am just trying to install SQL (Bin etc) on the D drive, I have a separate E and F drives for data and logs, that part is not an issue.

    Regards,

    D.

  • June 21, 2011 at 6:16 am

    #1341779

    Duran (6/21/2011)

    Hello,

    I'd imagine that somebody would have come across this before, I am trying to install SQL 2005 R2 (downloaded from MSDN) to install in the D drive, I specify the D drive during setup but this appears not to work as the engine and everything else ends up on C, is there a work around for this? Its just ridiculous. I understand that SOME things end up on C, but I know the difference. Any advice is appreciated.

    Thank you for reading,

    D.

    Duran see this post on the same issue:

    http://www.sqlservercentral.com/Forums/Topic1128324-1550-1.aspx

    AFAIK, the services must be installed on the %systemdrive%, with no choice whatsoever int he matter;typically the C: drive, but everything else, like tools, mdf's etc can be installed/moved elsewhere.

    i believe it's because SQL is being installed as a service,and needs to be on the same drive as the operating system.

    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!

  • June 21, 2011 at 7:40 am

    #1341837

    Hello Everyone, thanks for the input

    I'm not sure about this, I have installed SQL server in the D drive a number of times, in fact I have done it on UAT as well. When I get to the feature selection of set up, I can freely choose the D drive to install the bins (as I have done in the past), click next then click back and its changed to C. I wonder if there is something wrong with the set up of the server and luns etc.

    D.

  • June 21, 2011 at 8:00 am

    #1341850

    Hello,

    I did it in the end. I chose the D drive as normal, clicked next, it defaulted to C, changed it again, next, defaulted to C. Changed it again to show a work mate, clicked back, guess what? Stayed as D. When ahead with the installation and bins are now on D.

    Not quite sure why things went this way, but there you go.

    Thanks again,

    Regards,

    D.

Viewing 8 posts - 1 through 8 (of 8 total)

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