Multiple "Update All Indexes" running at once? (AREV Specific)
At 01 FEB 2000 11:08:05AM Michael Slack wrote:
We are running under Arev 3.12. We have a dedicated indexer for our Arev applications at our main office. The last couple of days, one of out remote sites has send us a rather large set of data transaction files. The data transaction files are how we keep the two data bases syncrhronize. Because our dedicated indexer (as it cycles thru the different applications) lands on and stays on the one application with the large number of transactions that have been loaded and that need to be indexed, we are running the "Update All Indexes" process while the dedicated indexer is turned off. You get to the process we are running from TCL by F10, DB Admin, Indexes, Update, Update All Indexes.
My question is, can we run the system's "Update All Indexes" process on several different work stations for the same application at the same time or not? None of use have every done it that way before, so we are uncertain if it will work or not. Our concern is that with multiple processes runing at the same time on the same application that there is a possibility that one or more may hang due to locking problems or that they are both trying to update the same data at the same time.
Can anyone tell me where I might find information on this subject to answer this question?
Thank you for your time.
Michael Slack
At 01 FEB 2000 07:44PM Warren wrote:
You can run several background indexing stations at the same time. This is what I normally do when there is large transaction backlog. Works fine in 2.0x so it should work even better in 2.1x+ without the !INDEXING choke point in 2.0x and lower.
The Update All Indexes is not a process that interrupts gracefully as the background indexing does.