Detaching Databases in MOSS 2007 Environments.

SharePoint 2007 : Réussir sa mise à jour vers le SP1

The Grib's Lair [Blog technique de Sébastien PICAMELOT] — Thu, 28 Feb 2008 00:22:01 GMT

J'ai encore très récemment pu voir une question sur le forum MSDN concernant une plateforme SharePoint

SharePoint 2007 : Réussir sa mise à jour vers le SP1

The Grib's Lair [Blog technique de Sébastien PICAMELOT] — Mon, 21 Apr 2008 13:36:42 GMT

J'ai encore très récemment pu voir une question sur le forum MSDN concernant une plateforme SharePoint

re: Detaching Databases in MOSS 2007 Environments.

jpw — Thu, 24 Apr 2008 21:45:01 GMT

Hi Cory,

Can you please clarify for me if you must use preparetomove when you remove the content databsae using Central Administration?

Does CA perform this step automatically, or is it required to run stsadm first?

Thanks,

Jason

Prepare Your Content Database

Vu's Technical Notepad — Fri, 02 May 2008 21:53:40 GMT

Before moving a content database from one farm to another, remember to prepare the database with the

re: Detaching Databases in MOSS 2007 Environments.

etsmtl — Thu, 31 Jul 2008 21:59:54 GMT

Hi,

I get exactly the same message (each hour). But when I run

stsadm -o sync -listolddatabases 0

I get an empty list.

And if I try to run

stsadm -o sync -DeleteOldDatabases 0

I get the error 7888

"A runtime exception was detected. Details follow.

Message: Invalid object name 'profile_stats'"

SP1 of WSS 3.0 and Office Server are installed.

Any idea ?

Thanks,

Marcelo.

Whole farm is down because timer jobs are not running

The SharePoint Farmer's Almanac — Thu, 09 Oct 2008 22:50:07 GMT

One of my clients this week managed to take his entire farm offline this week by upsetting the timer

How to properly move (Detach/Attach) a content database.

Microsoft Office Sharepoint Server 2007 — Tue, 28 Oct 2008 22:03:41 GMT

The idea to write this entry came as a result of many failed Profile sync operations I've seen lately,

re: Detaching Databases in MOSS 2007 Environments.

Victor Butuza — Tue, 28 Oct 2008 22:06:06 GMT

Pingback from http://blogs.technet.com/victorbutuza/archive/2008/10/28/how-to-properly-move-detach-attach-a-content-database.aspx

re: Detaching Databases in MOSS 2007 Environments.

rmzeitouny — Fri, 16 Oct 2009 08:42:46 GMT

Hi Corry,

i think that a little detail is missing from your post and that is in the command line:

stsadm -o preparetomove -contentdb sqlserver:dbname -oldcontentdb <GUID>

i think that the dbname should not be any database in your child farm but it should be the name of the new contentDB that used to have the oldcontentdb GUID in question, now i struggled a bit to find out how to get the new ContentDB for every old GUID in the list. and here is my solution:

1. Go to SQL server and select the records from the SSP database table "SiteSynch". It will look like

ContentDB id Site ID LastSync

01b05082-882e-4b6b-926b-9b18dbf6dee4 8d3b94be-812d-4dfa-b375-462754b7b9c2 15/09/2009 8:00:14 PM

2. Now you know the site ID for the OldDB GUIDs and you need to know the current ContentDB name. Execute the following code to get a list of site collections URLS and IDs with their content DBs (the WebAppUrl is the url for your web application)

public string[] EnumSiteColl(string WebAppUrl){

using (SPSite siteCollection = new SPSite(WebAppUrl))

{

SPWebApplication webApp = siteCollection.WebApplication;

string[] s = new string[webApp.Sites.Count];

int i = 0;

foreach (SPSite site in webApp.Sites)

{

s[i] = site.Url + ": " + site.ID + ": " + site.ContentDatabase.Name + ": " + site.ContentDatabase.Id;

i++;

}return s;

}