Home/ Questions/Q 231761
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T19:57:37+00:00

I’m using Linq2Entity for most of my database operations. However for database creation, table

  • 0

I’m using Linq2Entity for most of my database operations. However for database creation, table creation and initial data insertion I use plain SQL files. Therefore I need both an SqlConnection and an EntityConnection. Unfortunately the Entity Framework starts complaining that the Sql Server is not listening on the other end of the pipe.

I’m not sure what the problem is here, it could be due to user instancing. Clearing the pool of the SqlConnection or disposing the connection instance does not help.

The connection string I’m using is the following:

“Data Source=.\SQLEXPRESS; Initial Catalog=dbname; Integrated Security=SSPI;”

update:

I have tried to use the EntityConnection for database maintenance purposes but I’m running into troubles. I can’t use the EntityConnection to create databases and drop databases. The following syntax is unsupported for an EntityConnection but works fine for an SqlConnection to ms SQL express.

CREATE DATABASE silverfit ON ( NAME = silverfit, FILENAME = 'c:\silverfit\silverfit.mdf' );

Also for some reason the EntityConnection does not allow me to change databases which is necessary to drop a database. I’m afraid I still need the SqlConnection to create the database and tables..

Is there a way for SqlConnections and EntityConnections to coexist for local ms SQL express databases?

Thanks,
Wouter

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Have you tried creating a SqlConnection which you then pass to the constructor for your EntityConnection? One of the overloads for EntityConnection takes a MetadataWorkspace and a DbConnection (from which SqlConnection derives.) The slight drawback of this is that you must create your MetadataWorkspace manually, which gathers up the .csdl, .ssdl, and .msl files that define your workspace. However, in the long run, you should be able to share a single connection for both executing DML queries, and using Entity Framework.

    • 0