We have an EF edmx file in use to define the conceptual model of db. This is than used to access the database from our odata provider.The problem at hand is we have found that due to the size (very large) of the edmx certain things cause the EF to really bog down in certain situations. The main hit is relationships between tables. When a relationship is added between a table there seems to be an exponential growth in latency when odata or webapi surfaces that data.The situation is that we only use those relationships in 5% of all runtime cases.My question is, is there a way to dynamically change the edmx at runtime to add in the relationships when we require them so in the 95% of all other cases they don't affect performance? Is this possible to change edmx definition at runtime and are there repercussions to this?Thanks