dawnDBA
asked on
Sharepoint 2010 - 2 FARMS FROM 1 SQL SERVER
Hello Everyone,
I am mid-way through a project. We have decided it was necessary to rebuild our SharePoint 2010 environments. Due to a lack of resources we decided to utilize the same SQL Server for the new environment as the old, meaning temporarily we have 2 farms running from one instance of SQL. Everything has gone fine until now. I've made a copy of one of the content databases from the original environment, and restored it to another filename, and am trying to attach it to the new Sharepoint farm. It is not recognizing any of the site collections in it.
I have verified that the 2 farms are on the exact same version. And to make sure this is clear when I say two farms; I mean we have to completely distinct config db's running on the same instance of SQL. So this should remove the possibility of GUID conflicts... shouldn't it?
Thanks,
Dawn
I am mid-way through a project. We have decided it was necessary to rebuild our SharePoint 2010 environments. Due to a lack of resources we decided to utilize the same SQL Server for the new environment as the old, meaning temporarily we have 2 farms running from one instance of SQL. Everything has gone fine until now. I've made a copy of one of the content databases from the original environment, and restored it to another filename, and am trying to attach it to the new Sharepoint farm. It is not recognizing any of the site collections in it.
I have verified that the 2 farms are on the exact same version. And to make sure this is clear when I say two farms; I mean we have to completely distinct config db's running on the same instance of SQL. So this should remove the possibility of GUID conflicts... shouldn't it?
Thanks,
Dawn
Last Comment
ASKER
Thanks!
I understand this is not a best practice, and should clarify that it will be temporary. The old databases will be detached and removed once the new farm is stable.
You mention that "There can be many reason for sites not showing up" can you give me a few ideas? I'm out of ideas... I'll also clarify that Sharepoint is not giving me any error messages, it allows me to attach the content database, and if I query the db in SMS I see that the webs table does include the correct sites. But for some reason CA is showing me 0 site collections.
I understand this is not a best practice, and should clarify that it will be temporary. The old databases will be detached and removed once the new farm is stable.
You mention that "There can be many reason for sites not showing up" can you give me a few ideas? I'm out of ideas... I'll also clarify that Sharepoint is not giving me any error messages, it allows me to attach the content database, and if I query the db in SMS I see that the webs table does include the correct sites. But for some reason CA is showing me 0 site collections.
When you go to view all site collections it does not show any thing on the right like db name owner name if that's the case. U need to attach db again.
Check for the site collection administrator.
What about free disk space hope u have enough.
Check for the site collection administrator.
What about free disk space hope u have enough.
ASKER
I don't understand how free space could be related? I was able to restore the database to the instance successfully already. If I didn't have freespace it would have failed.
When I say zero site collections I mean CA>Application Management> Manage Content Databases. Here I see the name of my new content database, but under "Number of Current Site Collections" it says 0, and it should say 1.
When I say zero site collections I mean CA>Application Management> Manage Content Databases. Here I see the name of my new content database, but under "Number of Current Site Collections" it says 0, and it should say 1.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I finally figured out the problem, looks like it was just an oversight on my part. Both of the 2 backups that I had tried contained root site collections, and the web application I was trying to attach to already has a root. The problem is solved now.
Thanks for your help!
Dawn
Thanks for your help!
Dawn
Microsoft SQL Server 2008
Microsoft SQL Server 2008 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. Major improvements include the Always On technologies and support for unstructured data types.
50K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
There can be many reason for sites not showing up . Make sure the drives you are trying to restore on have enough space.
I agree I don’t think there will be any conflict in data base name because of that long guid .
you should atleast create a new instance and try there