Basic Data Modeling Patterns
[This content is no longer valid. For the latest information on "M", "Quadrant", SQL Server Modeling Services, and the Repository, see the Model Citizen blog.]
When you create models in Microsoft code name “M”, there are basic patterns that most models share. This section describes some of the most important and common modeling patterns in “M”. Note that this does not replace the "M" Programming Guide, and the topics in this section refer to the “M” documentation frequently.
These patterns apply to general “M” modeling. There are also modeling patterns that specifically apply to SQL Server Modeling Services. If you are targeting a Modeling Services database, you should also review the Modeling Services modeling patterns in “M”. For more information, see SQL Server Modeling Services Patterns.
In This Section
Using Modules to Scope the Model
Discusses the use of “M” modules to scope model or logical areas of a larger domain.
Using Extents to Define Entities
Shows how “M” extents provide storage for entities.
Defining Types for Reusable Data Definitions
Explains when to consider using “M” types, and shows how they assist with implementing common modeling patterns.
Choosing an Identity Field for each Extent
Explains the importance of “M” identity fields, and shows how to define them.
Adding References Between Extents
Shows how to use “M” to model relationships between extents.
Demonstrates the benefit on constraints in improving the consistency of data added to an extent.
Shows how to define a computed value that returns a custom set of fields from one or more underlying extents.
See Also
Concepts
Applying Common Modeling Patterns
Designing Models and Domains using "M"