How does the Entity Framework handle SQL Server Schemas?

Question

We are developing an application against a SQL Server 2005 database that uses several schemas for security purposes. The application will be using EF 2 in the .NET 4.0 framework.

What I'm wondering is how those SQL Schemas (Support, Admin, Employee) etc. can/will/should be represented on the EF side. Should I separate the various entities into separate models (edmx files) in the application to reflect the SQL schemas? I'm not as concerned about name conflicts as much as understanding the model more intuitively.

What are the recommendations or best practices in this area?

Thanks!

Answer 1

I have the same question in my mind.... if anybody knows, then it will be very helpful to me.