Basic Tenets of Designing for Performance
Designing for performance requires making trade-offs. For example, to get the best write performance out of a database, you must sacrifice read performance. Before you tackle database design issues for an application, it is critical to understand your goals. Do you want faster read performance? Faster write performance? A more understandable design?
Following are some basic truths about physical database design for SQL Server 2012 and the performance implications of each:
It’s important to keep table row sizes as small as possible. Doing so is not about saving disk space. Having smaller rows means more ...
Get Microsoft® SQL Server 2012 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.
