Re: Deadlock incidence greatly increased after upgrade from 11.5.1 to 12.5.3 - Suggestions?
- From: tomb@xxxxxxxxxxxxxxx
- Date: 4 Dec 2005 13:18:49 -0800
Mike Epprecht (SQL MVP) wrote:
> Hi
>
> No, you did not miss anything.
>
> The older system was probably disk bound, so queries were waiting on each
> other. You now have more processors and more RAM, so more queries will be
> run simultaneously, increasing the changes for deadlock.
>
> Look at the code and follow the basic rules of how to not create deadlocks.
> (http://www.sql-server-performance.com/deadlocks.asp a SQL Server link, but
> applies to Sybase too)
>
> We had this problem show up very prominently on an 11.9 to 12.5.1 upgrade.
> The new box was just so fast that the bad application coding from 6 years
> ago was starting to fall over itself.
>
> Regards
> --------------------------------
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
>
> IM: mike@xxxxxxxxxxxx
>
> MVP Program: http://www.microsoft.com/mvp
>
> Blog: http://www.msmvps.com/epprecht/
Thanks for the link Mike.
The new system is a single CPU box like the old one though, that would
exclude queries from executing simultaneously wouldn't it?
Tom.
.
- Follow-Ups:
- Re: Deadlock incidence greatly increased after upgrade from 11.5.1 to 12.5.3 - Suggestions?
- From: Mike Epprecht \(SQL MVP\)
- Re: Deadlock incidence greatly increased after upgrade from 11.5.1 to 12.5.3 - Suggestions?
- References:
- Prev by Date: Re: Deadlock incidence greatly increased after upgrade from 11.5.1 to 12.5.3 - Suggestions?
- Next by Date: next bugfix upgrade from 12.5.0.3 ESD4 is ?
- Previous by thread: Re: Deadlock incidence greatly increased after upgrade from 11.5.1 to 12.5.3 - Suggestions?
- Next by thread: Re: Deadlock incidence greatly increased after upgrade from 11.5.1 to 12.5.3 - Suggestions?
- Index(es):
Relevant Pages
|
Loading