Application Design Guidelines

Locking/deadlock considerations—These considerations are often the most misunderstood part of SQL Server implementations. Start by standardizing on update, insert, and delete order for all applications that modify data. You do not want to design in locking or deadlocking issues because of inconsistent resource locking orders that result in a “deadly embrace.” For a more in-depth discussion on locking and deadlocking and recommendations for avoiding locking performance issues, see Chapter 37.

Stateless application design—To scale out, your application needs to take advantage of load-balancing tiers, application server clustering, and other scaleout options. If you don’t force the application or database to carry ...

Get Microsoft® SQL Server 2008 R2 Unleashed now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.