Export (0) Print
Expand All

Relational (OLTP)---a Technical Reference Guide for Designing Mission-Critical OLTP Solutions

Want more guides like this one? Go to Technical Reference Guides for Designing Mission-Critical Solutions.

With the advent of relational databases in the 1970s, when Dr. E. F. Codd11 published his original work, the data types that were initially supported were well-structured types such as integer, decimal, float, and character. Most applications continue to store these data types for computation. However, non-structured data is now being captured and stored along with the traditional relational data. The schemas for the relational data predominantly remain the third normal form (3NF), and denormalization is occasionally adopted for better performance. The balanced B-tree indexes that are used for relational data are supplemented with sparse indexing, and row-level storage is enhanced with column-oriented storage. Volumetric statistics about the tables, rows, and columns are the foundation for the SQL Server Query Optimizer. However, volumetric statistics are being supplemented by "hints" when the complexity of the query is overwhelming and the optimizer needs manual help to provide consistent, good performance over a broad range of data that might not be distributed uniformly.

Best Practices

The following resources provide general reference material. (Note that the full URLs for the hyperlinked text are provided in the Appendix at the end of this document.)

Case Studies and References

Questions and Considerations

This section provides questions and issues to consider when working with your customers.

  • Customers have found the articles on SQL Server Performance.com12 useful in relation to performance tuning of SQL Server along, with the blogs from SQL Server MVPs such as Kimberly Tripp's blog13 and the blog aggregation on SQL

  • To effectively architect and design solutions, you should understand the type and volume of the data to be stored. If there is a need to store non-relational data in addition to the relational data, review the "Beyond Relational" Technical Reference Guide.

  • Microsoft StreamInsight which was introduced in SQL Server 2008 R2 should be considered in addition to a relational data store if any of the following considerations apply:

    • Is the data coming from process, manufacturing, or other real time systems?

    • Is rapid computation is required on a stream of data?

    • Is it possible that a "burst" of data may arrive out of sequence but still need to be processed as though it was received in order?

    • Is there a need for computation of results over a time window such as the need for the calculation of running averages, maximum values, or minimum values for the last three minutes of input streaming data?

  • Understand the characteristics of the data to see if you have sparse data. You might be able to use filtered indexes that are small, concise, and that provide good performance.

  • In general, relational data compresses well; compression ratios of 70% to 80% have been observed. Generally, for read-oriented workloads, compressed objects appear to provide good performance. If appropriate, ask for a sample of the data to see if it is possible to actually load and examine the compression that can be achieved.

  • Pure relational systems have been around for long time, with documented best practices for design, performance, availability, and manageability readily available in text books and SQL Server documentation. The importance of physical database design, application code interaction, and operational best practices is well understood, but at times, it is skipped because of time pressure. Be on the lookout for these elements.

  • Ask about the usage pattern and volumetric information to understand if the system needs to be designed for scale-out to meet the potential user and usage growth. Will a traditional scale-up system suffice?

  • When designing high-throughput transactional systems, choose the data access library carefully. For high-volume systems consider using pure ADO.NET. The ADO.NET Entity Framework and similar libraries can save development time, but it can be difficult to control the exact queries issued by the system.


Following are the full URLs for the hyperlinked text.

1 General Index Design Guidelines

2 Using Statistics to Improve Query Performance

3 Comparing Tables Organized with Clustered Indexes versus Heaps

4 Using Sparse Columns

5 Using Filtered Statistics with Partitioned Tables

6 The Many Benefits of Money…Data Type!

7 Best Practices for Semantic Data Modeling for Performance and Scalability

8 A relational model of data for large shared data banks by Dr. E. F. Codd

9 bwin: Global Online Gaming Company Deploying SQL Server 2008 to Support 100 Terabytes

10 ServiceU Corporation: Online Event Software Gets Disaster Recovery with SQL Server 2005 Database Mirroring

11 The Progressive Group: Progressive Prepares for Future Growth, Gains Agility with SQL Server 2005

12 SQL Server Performance.com

13 Kimberly Tripp's Blog

14 SQL Blog.com

© 2016 Microsoft