SDI Best practices (maintenance)

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

Description:
We opened the SDI feature in the Web OPAC to our libraries and are interested in getting info on the best practices to follow to avoid tablespaces to get full etc.

Our patron libraries will probably set up a big number of SDI queries to run on a regular basis, so the questions are:

1. What would be the ideal tablespace size for all relevant oracle tables (z323, z324, z325)

2. How often should we run p_sdi_02 to notify users their queries are about to expire?

3. How often should we run p_sdi_03 to delete expired SDI queries - will deleting these record really help reducing the size of the relevant oracle tables?

4. Are there other maintenance procedures you recommend?

Resolution:
1. Since Oracle tables get secondary allocations as necessary, the initial allocation is not so important. 10Meg should be a sufficient initial allocation.

2. We suggest running this once per week with the "Number of Days to Alert before SDI Queries Expire" set to "7".

3. We also suggest running p_sdi_03 once per week. It's hard to say how much space it will recover, but if it's not recovering much space, it should run very quick. Only if it's recovering more space would it take very long....

4. There are no other specific maintenance procedures we recommend.