Hi,
We have setup a SQL warehousing procedure via OI client server workspace. This procedure updates the SYSLISTS file using MFS (modified filing system).
We have found that if an OI table is updated quickly eg. via a file import, then some of the keys are missed in the warehousing procedure.
We think this is because a SYSLIST record is still being updated when it is processed and deleted by the warehousing procedure.
Is there any way to edit the XQ_MFS procedure to implement locking on the SYSLISTS table so that these records aren't warehoused until the MFS is complete.
Many thanks,
Steve Penney
ACA Group
Cape Town, South Africa
Steve,
I implemented my own SQL warehousing routine because I did not like the fact that Revelations saved changed keys into one row in SYSLISTS table. On a heavily used table I could imagine this causing performance issues.
In the short term, a way around your problem is to stop the warehousing while doing imports.
My project used a custom MFS to track changes into a log table where the key is table*key and the row contained date+time and type of change. The interface to SQL was handled as a batch process using ADO which is different than how the warehousing works.
I did my project before OI 9.2 came out so perhaps this has been resolved or redesigned. Special thanks to Bob Carten for his assistance.
HTH,
John