"Named instance" or "Default"?

  • I have a Default instance of Sql 2000 installed on a test box. I want to install a totally independent copy of Sql 2005 on the same test box. When the Sql 2005 Setup comes to the “Instance Name” box, I’m confused what to select: “Default instance” or “Named instance”. (I don't want to wipe out or upgrade the sql 2000 install.)

     

     

     

    TIA,

     

    Bill

  • A named instance.

  • why?


    Cheers,

    david russell

  • A named instanced exists side by side your SQL2000 "default" instance. During the installation process ,If you select default instance, you will overwrite your SQL 2000 instance..(that's in the "bad thing" category)

    for example, I selected named instance during installation and i named mine "SQL2005";

    when you connect via an application it is [MACHINENAME] for SQL 2000 and [MACHINENAME]\SQL2005 for the new instance.

     

    I've got SQL7 as a default, and SQL2000 and a SQL 2005 named instances, all coexisting nicely on my dev box.

    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!

  • I agree with Lowell.

    What confused me was this: when I think of instances I normally think of multiple copies of the same sql release installed on a box. Originally, I thought that one could have a Default instance of both sql 2000 and sql 2005 on the same box. But since the "Default" instance adopts that name of the machine I realized that I can't have two Default instances on the same box! So I need to use an instance.

     

    Bill

  • good answer.  thanks!

    much better than just blind instruction


    Cheers,

    david russell

  • Oooh, handbags at fifty paces! You asked a question, I gave you the right answer.

  • SQL Server 2005 Enterprise Ed. says it will upgrade a default instance of 2000 to 2005 but it will not overwrite your default 2000 instance with a 2005.  The database services part of SS2005 setup will fail.

    Although the SQL Server 2005 Enterprise Ed. setup screen says that you can upgrade the default instance it will not do it.  The very next screen will display the 8.00xxxx default instance already exists and will skip the installation of 2005 database services.

    Also, if you wish to make 2005 your default instance when 2000 already has one... This is one idea thay may help.  Create a named 2000 instance backup your 2000 instance files and restore them to your 2000 named instance you just previously created.  Then, under add\remove programs, delete the Microsoft SQL Server default instance.  After that you will be able to install or add a default instance for 2005.

    I just got done doing this very thing.

     

    Scott Blackford

    CIBER, Inc.

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

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