Anyone got any metrics on times taken for the offline compact to convert to ODS 48?
In my test environment it varies between 5GB and 1GB an hour. I expect faster on production servers, but with over 600GB of data on some servers, even at 20GB an hour we’re looking at 30 hours.
I also observed taht some databses increased in size as a result (though I’m sure document and design note compression will more than compensate for that)
Subject: Use indirect files
You can run several compact tasks in parallel. It’s the only way you’ll get through it. More here:
Subject: in parallel
thanks Susan. Running it in parallel had crossed my mind. I was going to do some tests to see if it made a difference to the overall time (or if there would be contention).
I wasn’t aware of these .ind files, but on reading about them I can’t see what they do that’s different from running multiple compacts on a folder by folder basis as I had been thinking of doing (via pre-prepared batch files)
thanks
Leon
Subject: Batch files work also
But this is the built-in method. I recommend using as many parallel compacts as you have processors, and 1 more if you have a large server and no users. Based on my experience (not testing), if you run 2 in parallel, it runs twice as fast, 3 is 3 times as fast, etc. By default, compact and updall and fixup all run serially.
Subject: thanks again