Re: Sybase vs Oracle - which is better?

In article <36547957.F17F975F_at_cvn.net>,

> Every morning new work would get loaded into the system by a batch process.
> Workers would then work this data to get it shipped out the door. Since the
 data
> is loaded in by
> a batch process it is put into the same data blocks. Since we had a 4K block
 size
> and the average
> row length is around 200 bytes we would have around 200 rows inside one block.
> I'm not sure how small your page locks could go but if I locked 200 different
> orders, remembering that since the data is all residing pretty much together I
> just put a major choke hold on the work flow for this process.
> Once this equipment is shipped out the help desk would tend to get more calls
 on
> the new clients and newly shipped pieces of equipment. Once again this data
 is
> pretty much grouped together in the database. If each helpdesk rep locked a
> couple of hundred rows when they are updating a client's information that
 would
> mean that other help desk reps would have to wait until they can do the same.
>
> So I guess I'm wondering how Sybase would deal with this problem and how small
 can
> a page lock be?
>

Firstly, a sybase page taking into account headers, etc, it about 1900 Bytes. This would mean, in your example, you would have to lock 9 rows at a time if you used page locking. If this was causing you major concerns, you could use ron locking which was introduced in version 11.9.0 (Current version is 11.9.3).

Hope this helps,

Leigh.

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Fri Nov 20 1998 - 00:00:00 CST