I have been using Sesame for a number of years now, first as a way of up-dating old Q&A databases and then to create many production and quality recording data. I have finaly got around to the last Q&A one that was programed about 20 years ago!
Our problem is that it is a serial numbering and repair database that has about 520,000 serial numbers in that the repair database looks up for origional information using the serial number as the shared key. This can take between 7 and 12 seconds which used to be instant in Q&A due to it's "Speedy" fields.
We are running the Sesame server on a HP Windows 2012 instance with 4 Gig of RAM and 2 CPUs, which does not seem to break a sweat during the XLookup process, 4% load at best. The Network is all Gigabite speeds.
I will increase the server to 8 Gig and 4 CPUs over the weekend to see if there is any improvement.
Looking through the Sesame manual it says it does not have the Q&A speedy fields because "In Sesame, fields are indexed as needed without user intervention."
Is there a way of forcing this or does anyone know anything about this process so that I can capitalise on it?
Am I just using too many records in one Data-bases?
Any views or advice would be helpful.
Thanks in advance