I have multiple existing SQL Server databases for different clients that have schemas that are 95% similar, but may have a few extra custom columns in each database to handle some specific customer need.
For example, database A might have a table with two custom columns:
StdColumn1, StdColumn2, CompanyACustom1, CompanyACustom2
and database B might have one custom column:
StdColumn1, StdColumn2, AnotherCompanyCustom1
and database C might have no custom columns, just:
StdColumn1, StdColumn2
I would like to configure Entity Framework so that the C# objects have some extra predefined properties (eg: CustomColumn1, CustomCustom2, etc.) that map to these custom columns if they exist, or have no effect if a custom column doesn't exist.
Views would be one way to do this, but I was wondering if I could use the CSDL, SSDL, and MSDL files to do something like this. Or perhaps this technology could be made to work?