|
|
Posted by Erland Sommarskog on 10/02/20 11:54
Jerry Hewett (jerhewet@yahoo.com) writes:
> "Erland Sommarskog" <esquel@sommarskog.se> wrote in message
> news:Xns980C634CC98A6Yazorman@127.0.0.1...
>
>> Maybe you can tell us a little more on what you want to achieve?
>
> Right now I'd be happy with even a minimal level of concurrency from SQL
> Server via multiple JDBC connections. :-(
>
> The code/SQL we're using works like a charm when stress- / load-tested
> against multiple users / threads under Oracle, Derby, MySQL, etc. but
> deadlocks constantly and consistently under SQL Server.
>
> So far WITH(UPDLOCK) doesn't seem to be doing much. Neither does
> selectMethod=cursor. I'm not a DBA, so I figure there must be something
> I'm not doing right (or not doing at all).
>
> Either that, or every other SQL database on the planet is a *LOT* more
> forgiving and/or better equipped to deal with deadlocks than SQL Server
> is. More than happy at this point to be proved completely wrong. ;-)
Different DB-engines have different architectures, and what works well on
one engine may not work well on another, even if the code as such is
portable.
Since you did not include any information of what you are actually doing,
it's impossible to assist further.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|