September 2010
Intermediate to advanced
1704 pages
111h 8m
English
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 2008 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 rows fit on a single 8KB page, which means fewer physical disk reads are required to read a given ...
Read now
Unlock full access