Kbase P11610: Relationship between Fetch Array Size and Shared Lock
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/19/2004 |
|
Status: Verified
GOAL:
Is there any relationship between Fetch Array Size and Share Locks?
FACT(s) (Environment):
Progress 9.1C
FIX:
There is no relationship between Fetch Array Size and Record Locking. Fetch Array Size controls how many records can be sent from the server to the client in one fetch. Setting it higher will result in more memory being used on the client and the server for holding records.
Controlling locking behavior has more to do with the Isolation Level for the transaction. To see only committed data and minimize share locks, the Read Committed isolation level should be used on the current record only. At this level, a share lock is held only long enough to read a record. So quickly, that it probably will not be observed in promon.
This can be set as the default behavior in the Data Source control panel applet.