Re: deadlock and high cpu - chicken or the egg

Thanks guys.

The overwelming consensus that the problem was indeed "db engine or
code related" was enough to =B8pressure/force the developper to have a
second look and they indeed realized that sybase <> mssql and thatr
they had to adjust some of the code. They fixed the problem in the
application code by tweaking something related to isolation levels.

Thanks all.

Re: deadlock and high cpu - chicken or the egg

Thanks for the followup. Always nice to hear what the result is.

And correct, Sybase != MSSQL. :-)





"Diggla" wrote in message
news:906428ad-062b-424d-911e-5ea888ed5266@1g2000hsl.googlegr oups.com...

Thanks guys.

The overwelming consensus that the problem was indeed "db engine or
code related" was enough to ¸pressure/force the developper to have a
second look and they indeed realized that sybase <> mssql and thatr
they had to adjust some of the code. They fixed the problem in the
application code by tweaking something related to isolation levels.

Thanks all.




--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html