As a side note to this. We found out a problem when doing QA on the
about to be released Emerald 2.5 update, that the instindx.sql script
was NOT being ran during the update. Everyone needs to execute that
script against their Emerald 2.5 upgraded database. This drammatically
affects consolidation and several other key performance issues. If
you have any questions about this, please let us know.
The script can take from a couple seconds to over an hour to run, based
on the size of your calls table. It will not hurt to run the script a
second time if you are unsure whether it was ran against your database.
Its also a good idea to run the checkdb.sql script after running the
instindx.sql, as it will update the statistics.
-- Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com