Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I would like to know if it's possible to create another instance of SQLServer 2005, to have 2 instances running on the same system ? thanks

share|improve this question

migrated from stackoverflow.com Feb 16 '10 at 21:02

This question came from our site for professional and enthusiast programmers.

    
SQL Server is software, it may be that the user is trying to do it programmatically. Clarify please. –  adolf garlic Feb 16 '10 at 21:01
add comment

5 Answers

Sure. One is the default instance, the other(s) is(are) a named instance.

This really does belong on serverfault.

share|improve this answer
add comment

Yes it is, that is what the Instance name is used for, when installing make sure you don't pick the default instance name but specify your own.

You can then connect to the instance using <SERVERNAME>\<INSTANCENAME> instead of just <SERVERNAME>

share|improve this answer
1  
They can also be instances of different versions of SQL Server too :) –  Russ Cam Feb 16 '10 at 21:01
add comment

No one has mentioned that this is done by doing a second install, from install media, of whatever version of SQL Server you want your additional instance to be. You don't do it by opened SSMS and making a new instance. You install the product again, and it makes a new install directory, a new SQL service, a new agent service, etc.

share|improve this answer
    
thanks, this little detail is really important for me. thanks again –  Tiberiu Hajas Feb 17 '10 at 1:23
add comment

You need to run the installer again, then choose a "named instance". You can install as many instances of SQL Server on the same machine as you like.

share|improve this answer
    
thanks, now i know how to do it. –  Tiberiu Hajas Feb 17 '10 at 1:24
add comment

Definitely you can. To add to the other answers, a few things to watch out for when using multiple instances:

  • TCP/IP port assignment - each instance is a separate process, and therefore needs to be run on its own port. (A single SQL Instance will happily run on 1433) The "proper" way to do this is to have your instances use dynamic port assignments, then make sure the SQL Browser service is running. The problem you run into with this approach (in a secured enterprise environment anyways) is it creates some headaches for your firewall administrators because they need to have a wide range of ports open to your SQL Server. The alternative is to run each instance on a static port.
  • Patching/Updates - make sure that both instances get any patches/updates you apply. This should be pretty easy because the patches are instance aware (you need to make sure all instances are checked when running through the patch installation) but I have seen people mess this up.
share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.