Minimizing Lock Contention

[PEdro]

Hi. I have the classic problem of multiple readers and writers hitting
a single table in Sybase (ASE 12.0, Solaris 8). Of course, lock
contention is occuring. One solution I know about from Syb 11.x is to
use "Heap Table Partition" (aka page chaining). In my case, I'll be
partitioning the table "trans" accross 3 segments (i.e: alter table
trans partition 3). I would like the opinion of this group on the
following:

1. There is a non-clustered, unique index on the table (trans_ndx1).
The readers use that index in their selects. Should I also move the
index to a separate segment (I don't even know if this is possible
using a partitioned table)?

2. Are there other solutions that are simpler/better in ASE 12.0?

Thanks in advance.

[Chief]

Yes you can move nonclustered index to a different segment, actually segment
of it's own. (Yes even though the table is partitioned) I generally create a
database on 3 different segments. One for only data, one for only
nonclustered indexes and one only for log. Let me know if you need the
steps involved in created an Index segment.

RK

"PEdro" <pedro...@gympartner.com> wrote in message
news:4a488596.01083...@posting.google.com...

[PEdro]

Thanks, RK. I tried that solution and it worked well, however, there
would be some (much less) lock contention during heavy periods.
Someone suggested the use of row locking, a fairily new feature in
Sybase. This has worked even better. My logs have not captured any
lock contention in 2 weeks!

If anyone has warnings/suggestions regarding row locking, please let
me know.

Thanks again.

"Chief" <kais...@yahoo.com> wrote in message news:<33Lp7.3088$2H2.1...@e3500-atl1.usenetserver.com>...