Tablespaces for parallel indexing: create new ones or use existing?

• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
We are setting up parallel indexing for a new bib library (abc02) that will be based on our primary bib library (abc01). The parallel indexing documentation on page 8 describes the process of setting up tablespaces for the new library - whether they are existing tablespaces or newly created ones.

Our question is this: how should we determine whether to create new tablespaces or use existing ones? We do have some free space in our current tablespaces, but we aren't sure whether the best practice is to create new tablespaces for parallel indexing or use existing ones. What do other sites do? Does ExLibris have a recommendation?

Resolution:
We recommend using the existing tablespaces in order to economize on space, but there is no strong argument one way or the other.

We strongly recommend using Logical Synonyms -- as described in Section 9, Option 1 --, *leaving* the new index tables in the parallel library. (That way, with subsequent indexing, you can have a second parallel library and just swap back and forth between the two. This is the most risk-free way to handle this.)

• Article last edited: 10/8/2013