Re: sysmaster database

Bill Weaver wrote: > > I have several SQL's that I use to monitor my system via sysmaster. While this > method has never been terribly speedy, it seems that these SQL's are taking > longer and longer to complete. Is there something I can do to speed up queries > against sysmaster? Should "update statistics" be run against it regularly even > though most of the tables aren't "real" tables? Could there be a problem with > multiple extents and if so, how do you fix that in sysmaster? There is nothing that you can do. The SMI tables represent data structures in shared memory that are usually linked lists. The longer your engine stays up the more randomized the lists become and the more a sequential element access will represent a non-sequential memory access. The only thing that may stave this off somewhat and reduce the effect is to make your shared memory segment resident if it is not already. This does not affect all SMI tables but it does affect many of them, those that live in the resident segment. Bouncing the engine should also clear up the problem for a while but it will be back. Art S. Kagel