> Is there anything I can do from the Enterprise Manager console or from
> within a JDBC connection to achieve the same effect as WITH(UPDLOCK)?
>
> Yes, I could change all of my SQL statements to include the lock... but
> isn't there any way to set or tweak something in SQL Server so that I
> won't have to hack a lot of code* to make things concurrent? Perhaps a
> way to set UPDLOCK as the default behaviour for the server, or schema,
> or table, or something?

"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?

> "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. ;-)