SQL Server Modeling Services Design 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.]
The SQL Server Modeling Services design patterns consist of guidelines for adding data to the SQL Server 2008 Modeling Services database. These patterns promote a consistent experience for users and tools that interact with the Modeling Services database. It also allows new data models in the Modeling Services to leverage specific Modeling Services services. Many of those services depend on data models to use proper naming conventions, SQL Server extended properties, or other database-specific implementation details.
In most cases, you should use “M” to model your data and apply specific Modeling Services patterns. This section discusses how to directly add data to the Modeling Services database without “M”. This is useful for an application that wants to add models and data to the Modeling Services database programmatically while still adhering to the Modeling Services design patterns. It also helps a model developer using “M” to better understand the implementation of the Modeling Services patterns that they utilize. For more information about how to use these patterns in “M”, see SQL Server Modeling Services Patterns.
Modeling Services Design Patterns
Refer to the following links for more information about specific Modeling Services design patterns.
| Design pattern area | Description |
|---|---|
Modeling Services uses SQL Server schemas to scope database objects, such as tables, related to the same problem domain. This topic discusses guidelines for using SQL Server schemas in the Modeling Services database. |
|
Modeling Services Folders act as logical containers for a collection of Modeling Services data. This allows for a more precise approach to security as well as improvements for versioning Modeling Services data. This topic discusses SQL guidelines for creating Folders. |
|
This topic covers specific SQL guidelines for creating Modeling Services tables. Some Modeling Services features require tables to follow naming conventions or contain special columns. |
|
Updatable views are a standard mechanism within the Modeling Services database for providing secure and flexible access to the underlying table data. This topic explains how to create an updatable view that aligns with the Modeling Services design. |
See Also
Concepts
SQL Server Modeling Services Architecture