[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 a new application, it is often best to design the application and its models in parallel. As the application adds new features and requirements, you can adjust the models to support those changes. The SQL Server Modeling CTP provides a language, Microsoft code name “M”, and tools that support this process.
Iterative Model Development
By iteratively developing the application and its models, you can more efficiently build a model that fully supports your application requirements. Although it is possible to develop complex application models before writing any code, it is very difficult to accurately anticipate all of the application's requirements. It is also difficult to spot errors or deficiencies in the model when the model development is separated from the application development.
Applications that use the SQL Server Modeling CTP technologies use the following pattern for parallel application and model development:
Create an application in Visual Studio 2010.
Create “M” files that define the model for the application.
Compile the “M” models and load them into a target SQL Server 2008 database.
Write application code that reads and writes to that database representation of the model.
Iteratively change the application code and the model code during the application lifecycle.
There are several choices for updating the “M” models in the database. The “M” code can be created and managed from within Visual Studio 2010, or you can write and build the models outside of Visual Studio 2010. For more information, see Updating Models in the Database (SQL Server Modeling CTP).