I have a problem with the Full Import of AD profiles to the Profile Database. I
run a full import every night at 11 PM. For a few weeks now, it takes more than
10 hours to complete, and the import does not make correct updates.

I also have a test configuration in which the import runs with the same
parameters and on the same Active Directory (same domain, same controller) as in
production (but is run by a different SPS server and updates a different SQL
server instance). The test import runs in about 15 to 20 minutes and the test
profile DB is up to date.

Does anyone know why this is happening ? I have the feeling that my profile DB
is corrupt.

Questions: is there a way to drop it and recreate it from scratch and running a
full import without impacting the other SPS databases (SITE, SERV and the config
DB) ? Or can I take the profile DB from my test environment and copy it to the
SQL server in production harmlessly ?