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

We are setting up a new SharePoint 2010 QA server and would like to use the same SQL server as our SharePoint 2007 QA server. Are there any issues or gotchas with this strategy?

share|improve this question
up vote 1 down vote accepted

That should work just fine. You don't need separate SQL instances either, just make sure you don't do the 'all in one, let the SharePoint installer sort everything out' install.

This is assuming that your SP2010 and SP2007 servers are 2 separate (virtual) servers talking to the same SQL database server.

share|improve this answer
Thanks, do you know if content deployment would be effected in this model? Where QA 2007 deploys to prod 2007 and now I want to start creating 2010 DBs in the same SQL instance as QA 2007. – jjr2527 Feb 16 '11 at 21:19
Yes, the front end and app servers are separate from the SQL host. – jjr2527 Feb 16 '11 at 21:22
I don't anticipate any interference between the 2. – Muhimbi Feb 17 '11 at 7:52

There shouldn't be a problem as long as you use separate SQL instances for 2007 and 2010 on the same server. They will operate independent of each other so no problems should arise.

share|improve this answer
No need for 2 different SQL Instances. We host 10 SharePoint instances (2007 and 2010) on the same SQL Server Instance just fine. – Muhimbi Feb 16 '11 at 18:01

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.