Reputation: 6619
I just converted a MySQL database to SQL Server. I'm complete new to SQL Server, I want to use it with Entity Framework 4, so I shouldn't be a biggie.
I think I don't get the concepts about objects in DB and so on. In SQL Server Mgmt Studio I can execute this query
/****** Script for SelectTopNRows command from SSMS ******/
SELECT TOP 1000 [id]
FROM [db].[dbo].[mytable]
And it works fine, however if I use this connection string
Data Source=MYPC-PC\;Integrated Security=SSPI;Min Pool Size=5;Max Pool Size=60;Connect Timeout=30
The query will execute fine, but it will exclude the [db], so it will not return any row. This is the query from Entity Framework.
/****** Script for SelectTopNRows command from SSMS ******/
SELECT TOP 1000 [id]
FROM [dbo].[mytable]
If I change my connection string to include a Database like this
Data Source=MYPC-PC\;Integrated Security=SSPI;Database=db;Min Pool Size=5;Max Pool Size=60;Connect Timeout=30
I get this error
There is already an object named 'MyTable' in the database.
But there is only one table called Table
. I have no idea of the concepts behind this. What am I doing wrong? I'm using SQL Server 2012
I use code first.
var result = db.MyTable.Where(x => x.Prop == Prop)
.OrderBy(x => x.Something)
.Take(10);
var data = result.ToList();
My DbContext class
public class Context : DbContext
{
public Context()
: base("Context")
{
// Get the ObjectContext related to this DbContext
var objectContext = (this as IObjectContextAdapter).ObjectContext;
// Sets the command timeout for all the commands
objectContext.CommandTimeout = 12000;
}
public DbSet<Models.MyTable> MyTable{ get; set; }
}
And in web.config
<connectionStrings>
<add name="Context" providerName="System.Data.SqlClient" connectionString="connectionString" />
Upvotes: 0
Views: 1607
Reputation: 841
Your table MyTable
already exists in the database before first migration. So you can just delete this table and then it will be recreated at first application run.
EDIT:
If you don't want to remove your table and if you use at least EF 4.3 then
run from the Console Add-Migration InitialMigration -IgnoreChanges
and then run Update-Database
Upvotes: 2