Data is the most important outcome of any software application. When a technology company is acquired, the most important assets are the customers, the data, and the software, with priority generally in that order, and in enterprise scenarios, data will outlast the applications that generate and manage it by many generations. Development tools generally consider the database as a second class citizen, and that is no more apparent than with Entity Framework functionality, which is the default data access technology for .NET applications. The orthodox Entity Framework (EF) experience is for developers to write .NET classes that contain data storage attributes and then for tooling to develop the schema management scripts. This is great for small applications, but as an application grows and data specialists are bought onto teams, EF code-first development can become a nightmare, with demarcation disputes over schema control common.