Check the instructions in the lower section of the page:

 

http://blogs.technet.com/corybu/archive/2007/06/01/detaching-databases-in-moss-2007-environments.aspx

 

Basically:

 

First we need to find out which databases are currently not in sync, this can be done from a simple stsadm command on your SSP web front end.

 

stsadm -o sync -listolddatabases 5

 

This command will list all databases that have not synced up correctly with the SSP in greater than 5 days.  Based on your schedule to index your age value may change.  You may want to change this value to 10 or 15.  The result set returned is a list of database GUID’s and the date/time they were last synchronized. Now that we have determined the list we need to clean them up and get those guys synced.  To do this we execute an stsadm command that sets all of those GUID’s as old, then during your next index it will pick up the new GUID’s for your production databases not currently being synced.

 

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

 

where sqlserver is where your content is housed, dbname is any database in your child farm, and GUID is a guild from the list of non-syncing databases we generated with the command above.

 

Based on your crawl schedule wait until the next full crawl.  Once it completes go back into your SSP and run the stsadm -o sync -listolddatabases 5 command again.  Anything left can likely be removed at this point.  You can remove what is left by running the following command.

 

stsadm -o sync -deleteolddatabases 5

 

this will delete all GUID entries in the SSP for anything that is out of sync for more than 5 days.  You have now successfully cleaned all inconsistencies with syncing in your SSP.  All out of sync alerts should now subside.

 

Remember use stsadm -o preparetomove before detaching a database and this will not be a problem!