On 9/25/05 7:02 PM, "Paul Berkowitz" <[EMAIL PROTECTED]> wrote:
> But rebuilding the database _also_ compacts it. There's no need to do both > if you're going to rebuild. Rebuilding copies data to a new database, > creating new IDs and links. It doesn't copy empty spaces any more than > "Compact" does. So it compacts just as effectively. (Compacting doesn't > assign new IDs or links.) I may have misunderstood what Jud said (a while back on this list) when I asked him about Compacting vs. Rebuilding: >> I am saying that they are two completely different things. Compact is >> something you should do when you want to get rid of unused space in your >> database. It should leave your database with the exact same dataset that you >> started with. >> >> Rebuild is to be used when there is something wrong with the structure of >> your database. It is a lossy action. It will flush all of your IMAP caches, >> it will not retain the links that have been defined, it will possibly not be >> able to preserve all of your data and it might resurrect data that was >> previously deleted. >> >> More than likely a rebuilt database will be smaller than a compacted one but >> it goes about doing things in a much different manner. I would never rebuild >> a production database unless I was sure it was damaged. What you said above may have clarified it for me. But then, what would you recommend that Arkady do before the import: Compact or Rebuild? Beth -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
