Concurrency recommendations for database designers

Database designers can take certain general actions to promote concurrency without compromising data integrity.

To promote concurrency without compromising data integrity, use any of the following approaches:

• Keep like things together in the database.
• Keep unlike things apart from each other in the database.
• Use LOCKSIZE ANY or PAGE as a design default. Consider LOCKSIZE ROW only when applications encounter significant lock contention, including deadlock and timeout.
• Examine small tables, looking for opportunities to improve concurrency by reorganizing data or changing the locking approach.
• Partition secondary indexes to promote partition independence and reduce lock contention.
• Minimize update activity that moves rows across partitions.
• Store fewer rows of data in each data page.