[This is prerelease documentation and is subject to change in future releases. Blank topics are included as placeholders.]

The topics in this section describe several common data modeling design patterns. The context in which each pattern should be considered is discussed using a simple example with sample Microsoft code name “M” code written in a compact extent-oriented style. Examples are drawn from a simple personal contacts domain, which, while not typical of the kinds of model that can be stored in the repository, is easily understood.

Guidelines for Model Patterns

See Also