This is a multi-part message in MIME format.
Content-Type: text/plain; charset=us-ascii
We are running an OLTP (multiple readers, one writer) environment with
Microsoft SQL server. I was hoping to get some suggestions on how we
can increase concurrency on the database.
The database is being used as a repository for stock quote data. Users
are constantly retrieving stock quotes. Meanwhile, the stock feed
processor is writing into the same table. So while the update is
happening, everyone gets locked out.
I am looking for a way to increase the concurrency on the system. For
example, if a quote is being updated, I'd like the user to get old data,
rather than have to wait for the update to finish. Unfortunately there
doesn't seem to be a way to do this in Sybase/MS-SQL. I have tried
using dirty reads, with limited success (comes back quickly, but
sometimes doesn't return data).
Does anyone have a suggestion on how to resolve this problem? Do other
database vendors (relational or object) handle this situation more
gracefully? Would row-level locking on Oracle or some other database
make a huge difference?
I'd appreciate any advice.
The Daily Rocket Company
Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf"
Content-Description: Card for Burtin, Boris
Content-Disposition: attachment; filename="vcard.vcf"
fn: Burtin, Boris
org: The Daily Rocket Company
adr: 655 Castro St. #8;;;Mountain View;CA;94041;USA
tel;work: (415) 903-1701
tel;fax: (415) 903-1705
tel;home: (415) 321-9358