Question

I have a script running every hour that stores log data in a logging database. Every month a new table is created, and the logging information from this month is stored in that table.

Every table that is created is identical and match a simple POCO class

class IISLog
{
  SystemRef,
  date,
  s-sitename,
  //etc
 }

I’ve only found a single way to access these tables using a code-first approach:

 var result = this.Database.SqlQuery<WebLog>("select * from " + table + "_" + month);

However, it appears that I lose the lazy loading in the process since SqlQuery returns an IEnumerable of the type.

Is there any way to let lazy loading prevail as well as allow the data context to track the elements? (Main priority on the first point).

Answer 1

You will lose everything by using SqlQuery – that is direct SQL execution without any EF features involved. It will just materialize objects for you.

There is no way to use EF with this type of database tables. EF demands that type can be mapped only to single table (or set of tables in case of inheritance or splitting). Entity cannot be mapped to multiple tables even if they are exactly same.

If you want to use EF you should look for solution on database side and map only single database view or table to your entity or use stored procedure to correctly select table which will be queried.