SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm setting up three SharePoint instances. We have a single database instance (DB\SP2010) that will hold all the databases for these three SP instances. Will this be overly confusing? Is there some way I can create prefixes for the databases upon install?

I'm contemplating just creating three db instances (DB\SPDev, DB\SPDemo, DB\SPTest).

What do you recommend?

To answer Mike's question, Demo could be considered production, but Dev & Test are for dev & test, respectively. This question isn't so much out of a performance consideration (it's one database server regardless) but more of a configuration consideration.

share|improve this question
I guess it depends on what you are using the sharepoint instances for. Is one production and two development? – Mike Nov 30 '11 at 15:58
@Mike see the updated question. – Nathan DeWitt Nov 30 '11 at 16:13
up vote 1 down vote accepted

Each instance of SharePoint can spawn between 8 and 20+ databases and not all databases are created as part of the SharePoint installation (i.e. Web Applications and Service Applications are usually configured later as needed), I would strongly advise putting each SharePoint farm in its own instance of SQL.

Another "neat" feature of SharePoint is that, for certain operations that ask for a database name, if you specify a database name that already exists then SharePoint will happily append new data into the old database without warning you, possibly resulting in two farms being tied into the same database. This risk is also greatly minimized when the farms are in separate instances.

If you are a "Separation of Duties" shop, then odds are also good that you have security requirements where certain people can only take certain actions in certain environments. Having all of your farms in the same instance makes managing this a great deal more complex.

If one of your environments is Production then you also have to worry about overall performance as SharePoint hits TempDB quite hard. Having all three farms in one DB Instance means that all farms will be fighting over a single TempDB. This means that normal developer activities could easily bring your production performance to a halt.

Multiple instances is additional overhead but makes management, backups and security a great deal easier. SharePoint also performs better this way.

share|improve this answer
This is a great response. While it is technically possible to install multiple instances in one database, your cautions are worth noting. – Nathan DeWitt Dec 2 '11 at 20:03

Yes, you can do a SharePoint 2010 install in a manner that will allow you to specify the names of all your SharePoint databases, so you can enforce a naming convention that you can use to distinguish between the various farms that the databases are associated with. The challenge is that you won't be able to use the Product Configuration Wizard GUI interface to make this happen, instead you'll have to do it via the command line with PSCONFIG.exe and PowerShell.

The good news is that there are a couple of good write-ups out there that describe the steps you'll need to take to make it work. I'd suggest taking at a look at these posts:


share|improve this answer
excellent resources! Thanks! – Nathan DeWitt Dec 1 '11 at 18:24

Your Answer


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.