Entity Framework

Migrations

Using EF 4.3 Code First Migrations with an Existing Database

In working on my upcoming EF 4.3 Migrations video for Pluralsight , I wanted to work out how to use this with an existing database where I plan to add new types and therefore want migrations to not just use this database, but migrate it as well. Problem solved*, but then I tried to use it in a production application and found an easy-to-fix problem. So…I thought I’d share the process in a blog post while it’s on my mind.

As shown in the previous precompiled view blog ( Isolating Performance with Precompiled/Pre-generated Views in the Entity Framework 4 ), views can significantly improve performance in various scenarios such as first-run; memory usage; and execution of one-off queries. However, the creation of views for large complex models that consist of many entities and associations), can create lots of views which in turn will require heavy use of strings, and reach the .NET metadata format limit on the number of user string characters (0xFFFFFF).

http://blogs.msdn.com/b/appfabriccat/archive/2010/08/30/solving-the-no-logical-space-left-to-create-more-user-strings-error-and-improving-performance-of-pre-generated-views-in-visual-studio-net4-entity-framework.aspx

Solving the “No logical space left to create more user strings” Error and Improving performance of Pre-generated Views in Visual Studio .NET4 Entity Framework - Windows Server AppFabric Customer Advisory Team

EDMGEN ViewGeneration takes hours

http://social.msdn.microsoft.com/Forums/en-US/adodotnetentityframework/thread/467ea49d-2733-41a9-b3e9-dcfe85b8c05a

We're using code-first with 500+ entities.

This topic describes performance characteristics of the ADO.NET Entity Framework and provides some considerations to help improve the performance of Entity Framework applications. Stages of Query Execution

http://msdn.microsoft.com/en-us/library/cc853327.aspx

Performance Considerations (Entity Framework)

LINQ To SQL LIKE Operator - Generating LIKE in SQL Server Statements

http://devio.wordpress.com/2010/01/28/tracing-sql-statements-generated-by-entity-framework/

Tracing SQL Statements generated by Entity Framework « devioblog

The DataContext of Linq2Sql provides a Log property that one can assign a TextWriter to retrieve the text of the SQL statements generated by Linq.

The DbContext API introduced in Entity Framework 4.1 exposes a few methods that provide pass-through access to execute database queries and commands in native SQL, such as Database.SqlQuery<T>, DbSet<T>.SqlQuery, and also Database.ExecuteSqlCommand.

Stored procedures with output parameters using SqlQuery in the DbContext API - Diego Vega

http://blogs.msdn.com/b/diego/archive/2012/01/10/how-to-execute-stored-procedures-sqlquery-in-the-dbcontext-api.aspx

Code-First Development with Entity Framework 4

.NET 4 ships with a much improved version of Entity Framework (EF) – a data access library that lives in the System.Data.Entity namespace. When Entity Framework was first introduced with .NET 3.5 SP1, developers provided a lot of feedback on things they thought were incomplete with that first release.

Issuing SQL in Entity Framework

http://visualstudiomagazine.com/articles/2011/05/17/wcnet_issuing-sql-in-ef.aspx

Practical .NET

Updates in Entity Framework

Practical .NET

Some Bumps in the Separation of Entity Framework and .NET Framework

http://visualstudiomagazine.com/blogs/data-driver/2011/10/entity-frameworknet-framework-separation-not-so-smooth.aspx

Some Bumps in the Separation of Entity Framework and .NET Framework