Hi,
I recall from some years ago that Oracle and db2 have some mechanism where, upon startup, you can force a table or tables to 'live' in memory--I'm not talking about caching--I mean just read/write from memory and only updating the disk infrequently (accepting data loss if there is an abend). Does sql7 have such a command?
This would be for smaller, highly volatile but less critical data, such as a tracking table, that tracks information that changes rapidly. If the machine crashes, that data is invalid anyway, so the fact that the lastest disk update was not made is not important, which is why I want it in memory, but I don't know of a suitable messaging protocol where I could peek into the servers memory from a client over tcp/ip or push array data to the clients over tcpip, so the memory array is not an option (unless you know of another way).
Basically, I have data from a usb port that will be updating this table every second or so, and this table will be read by many clients over a network at close intervals (a read every 5 seconds or so--but by 100 clients).
I don't want the server's disk going crazy over this. This data in this table would have *some* data from the other tables in the db, but that portion would change only every few minutes. Thanks for any ideas...
--Jim
I recall from some years ago that Oracle and db2 have some mechanism where, upon startup, you can force a table or tables to 'live' in memory--I'm not talking about caching--I mean just read/write from memory and only updating the disk infrequently (accepting data loss if there is an abend). Does sql7 have such a command?
This would be for smaller, highly volatile but less critical data, such as a tracking table, that tracks information that changes rapidly. If the machine crashes, that data is invalid anyway, so the fact that the lastest disk update was not made is not important, which is why I want it in memory, but I don't know of a suitable messaging protocol where I could peek into the servers memory from a client over tcp/ip or push array data to the clients over tcpip, so the memory array is not an option (unless you know of another way).
Basically, I have data from a usb port that will be updating this table every second or so, and this table will be read by many clients over a network at close intervals (a read every 5 seconds or so--but by 100 clients).
I don't want the server's disk going crazy over this. This data in this table would have *some* data from the other tables in the db, but that portion would change only every few minutes. Thanks for any ideas...
--Jim