Dear NN,
You'll always see the 100% for max memory because, if you have the parameter "allocate max shared memory" config parameter (value = 1) enabled.
This parameter indicates that we will allocate all your max memory during startup. And if this is not enough a message will be returned and ASE will not start at all.
Regarding the parameters you mentioned, open indexes and partitions. There are no real risks, but will have your performace impacted.
I will suggest you to check Num_active,Pct_act, Reuse_cnt, Max_Used etc:-
Any reuse usually (but not always!) implies that resource should be tuned a little higher. Similarly if we see a large gap between max used and the actual amount configured, we suspect (most of the time) we could lower that resource.
use sp_countmetadata config name, db_name ( During OFF peak hours )
increase theses parameter to 10% more as shown in sp_countmetadata output.
Have you changed your max network packet size, in recent past? Check the Sybase Infocenter article which details you abut estimating the max additional network memory.
Perhaps a more useful place to start is with sp_sysmon. It gives you pretty detailed information about all the major aspects of your running database sampled while your application is actually running.
Regards,
Ajith Prabhakaran