Hi, We have staging environment for MOSS-2007 server, which is cloned from Production environment. Due to having cloned from Prod, staging server Center Administration site is pointing to Production environment content database. Now we have dedicated Content database server for staging environment, which is restored from Production and we want to make staging environment point to this new dedicated Staging content database server. Hence please help me if any one came across this scenario with possible solutions to point Staging environment to specific content database server? Thanks & Regards, Suresh Channam

First I should point out that having two farms accessing the same database is unsupported (content, service, or configuration). When you say you cloned production, I'm assuming you copied a VM? Your staging environment should have an entire set of its own databases. Are you sure the other databases in the farm are not still pointing to production? To answer your question, to change the location of the content database, see Attach or detach content databases (SharePoint Server 2010). I would be careful however, detaching the database from staging may impact the database in production. To be honest I would recommend throwing out your clone and creating a new VM from scratch with a new farm and then attach the a copy (or backup) of content databases. Jason Warren Infrastructure Specialist Habanero Consulting Group habaneroconsulting.com/blog

Hi Jason, Thank you for your inputs in this regard. Sorry for delay in my response. For the query mentioned in your inputs regarding dedicated set of databases in staging, Staging environment is not having dedicated content databases and as I mentioned, content database setting in Central administration is pointing to production environment. Some time back, this staging environment cloned from prod but never used. Cloning not done for Content databases. And hence staging environment setting still pointing to prod environment. Now we have prepared dedicated staging database server and copied prod content databases to this new dedicated staging server. And we need to make this staging environment functional using dedicated staging environment content databases. So, from your inputs, best approach for given scenario is to create new VM from scratch? Thanks & Regards, Suresh Channam

Hi Jason, Thank you for your inputs in this regard. Sorry for delay in my response. For the query mentioned in your inputs regarding dedicated set of databases in staging, Staging environment is not having dedicated content databases and as I mentioned, content database setting in Central administration is pointing to production environment. Some time back, this staging environment cloned from prod but never used. Cloning not done for Content databases. And hence staging environment setting still pointing to prod environment. Now we have prepared dedicated staging database server and copied prod content databases to this new dedicated staging server. And we need to make this staging environment functional using dedicated staging environment content databases. So, from your inputs, best approach for given scenario is to create new VM from scratch? Thanks & Regards, Suresh Channam

Yes. Usually I'll build a staging environment that is configured nearly identically to production. Exceptions may include URLs, AAMs, service accounts, etc, though the configuration (services, web applications) and content are usually the same (take a backup of production content and restore in staging). In most cases I use the same script that I have built for the farm and make minor changes (URLs, server names, etc) and use it to configure both environments. Jason Warren Infrastructure Specialist Habanero Consulting Group habaneroconsulting.com/blog

Thanks Jason for your confirmation in this regard. So, If I go for Un-Installation of existing Sharepoint in my staging server then what will be settings or pre-requisites that I need to check before un-installation. Why because, my staging server currently tightly coupled with PROD environment by having content database mapping for Central admin pointing to PROD server. So, if I done any changes in staging then it will reflect respective changes in PROD content database. Hence To have safe un-installation, how can I detach existing sharepoint installation of Staging from mapping with PROD content database before Un-Installation to make sure that Un-Installation will not touch PROD databases? Thanks & Regards, Suresh Kumar Channam

Suresh, Instead of uninstalling, you can restore your staging environment to just bare metal with just Operating System and start the installation from there - Prerequisites, SQL Server, and then MOSS. Remember to install the same version (cumulative updates and service pack) of SharePoint as your production. Once you have SharePoint installed, you can start installing the customizations (solutions, features, infopath forms, etc.) At this stage you can also copy (page by page) the configuration from your production Central Admin to your Staging Central Admin. You can then attach the backups of your production content databases which should bring across all contents, permissions, etc. That's how we did it and it worked well for us! Hope this is helpful to you too. Regards, JeremyJeremy Ramos | .NET / SharePoint / Dynamics Developer

Why because, my staging server currently tightly coupled with PROD environment by having content database mapping for Central admin pointing to PROD server. So, if I done any changes in staging then it will reflect respective changes in PROD content database. Hence To have safe un-installation, how can I detach existing sharepoint installation of Staging from mapping with PROD content database before Un-Installation to make sure that Un-Installation will not touch PROD databases? Your concern is the reason why having multiple farms sharing databases is unsupported. I honestly don't know if there is a way to remove the staging server without impacting the databases. Even wiping the server may have unexpected results if the configuration expects this server. Jeremy's approach is what I would do -- simply restore the staging server back to just the OS (or create a new VM), don't bother trying to uninstall gracefully. I would also recommend taking a backup of production before you start in case you need to rebuild prod. The approach I would take is to make SQL backups and restore individual databases as needed, or rebuild the production farm (that is reinstall and configure it) and restore the content databases. Jason Warren Infrastructure Specialist Habanero Consulting Group habaneroconsulting.com/blog

Hello As that is Pointing to Production DB Server and Database,You can backup the database and restore it to staging environment Then you can use stsadm -o addcontentdb to attach the Central Administration dB to CA

Hello As that is Pointing to Production DB Server and Database,You can backup the database and restore it to staging environment Then you can use stsadm -o addcontentdb to attach the Central Administration dB to CA