OCSDTech
asked on
Content database attach and detach - does it leave residue in the farm?
We have a SharePoint 2010 farm in the implementation stage. We attached a SharePoint 2007 content database so we can see how it would upgrade. We plan to detach the content database since this is just a test. My colleague would like to roll the databases and server back to the time before the attach was done because of concerns that residue from the attach may be polluting the farm. What do you think? Thanks!
ASKER
The server is preproduction and I think that's why my colleague is concerned. We'll be rolling back the databases and the virtual machine back to the same date time so they should match.
The concern regarding the attach and detach of the content databases is that there are services that are shared such as search, profiles, bdc, managed metadata, etc. that may be polluted by the action of attaching the content database. I'm assuming that those services will clean themselves of references to content in the detached databases and I would like to confirm this. Thanks!
The concern regarding the attach and detach of the content databases is that there are services that are shared such as search, profiles, bdc, managed metadata, etc. that may be polluted by the action of attaching the content database. I'm assuming that those services will clean themselves of references to content in the detached databases and I would like to confirm this. Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your help.
Technically (as long as the method for rolling back is sound) there should be no problems with this, howeever, any changes are stored in the content database and not in binaries on the fielsystem itself.
If this is your production server I understand but I think perhaps a little bit paranoid? Is this a production or dev server/farm?