There is already an object named in the database

Question

Update-Database failed from Package Manager Console  I ve used Entity Framework 6 x and code-first approach  Error is   There is already an object named  AboutUs  in the database    How can I solve this problem   internal sealed class Configuration        DbMigrationsConfiguration lt Jahan Blog Web Mvc Models JahanBlogDbContext gt        public Configuration                 AutomaticMigrationsEnabled   true          AutomaticMigrationDataLossAllowed   false             protected override void Seed Jahan Blog Web Mvc Models JahanBlogDbContext context                   My DbContext is   public class JahanBlogDbContext   IdentityDbContext lt User  Role  int  UserLogin  UserRole  UserClaim gt        public JahanBlogDbContext             base  name JahanBlogDbConnectionString                 Database SetInitializer new DropCreateDatabaseIfModelChanges lt JahanBlogDbContext gt                protected override void OnModelCreating DbModelBuilder modelBuilder                modelBuilder Conventions Remove lt PluralizingTableNameConvention gt             modelBuilder Entity lt Comment gt    HasRequired t   gt  t Article  WithMany t   gt  t Comments  HasForeignKey d   gt  d ArticleId  WillCascadeOnDelete true           base OnModelCreating modelBuilder            modelBuilder Entity lt User gt    ToTable  User            modelBuilder Entity lt Role gt    ToTable  Role            modelBuilder Entity lt UserRole gt    ToTable  UserRole            modelBuilder Entity lt UserLogin gt    ToTable  UserLogin            modelBuilder Entity lt UserClaim gt    ToTable  UserClaim               public virtual DbSet lt Article gt  Articles   get  set        public virtual DbSet lt ArticleLike gt  ArticleLikes   get  set        public virtual DbSet lt ArticleTag gt  ArticleTags   get  set        public virtual DbSet lt AttachmentFile gt  AttachmentFiles   get  set        public virtual DbSet lt Comment gt  Comments   get  set        public virtual DbSet lt CommentLike gt  CommentLikes   get  set        public virtual DbSet lt CommentReply gt  CommentReplies   get  set        public virtual DbSet lt ContactUs gt  ContactUs   get  set        public virtual DbSet lt Project gt  Projects   get  set        public virtual DbSet lt ProjectState gt  ProjectStates   get  set        public virtual DbSet lt ProjectTag gt  ProjectTags   get  set        public virtual DbSet lt Rating gt  Ratings   get  set        public virtual DbSet lt Tag gt  Tags   get  set        public virtual DbSet lt AboutUs gt  AboutUs   get  set        Package Manage Console   PM gt  update-database -verbose -force Using StartUp project  Jahan Blog Web Mvc   Using NuGet project  Jahan Blog Web Mvc   Specify the  -Verbose  flag to view the SQL statements being applied to the target database  Target database is   Jahan-Blog   DataSource   local   Provider  System Data SqlClient  Origin  Configuration   No pending explicit migrations  Applying automatic migration  201410101740197 AutomaticMigration  CREATE TABLE  dbo   AboutUs         Id   int  NOT NULL IDENTITY       Description   nvarchar  max        IsActive   bit  NOT NULL       CreatedDate   datetime        ModifiedDate   datetime       CONSTRAINT  PK dbo AboutUs  PRIMARY KEY   Id     System Data SqlClient SqlException  0x80131904   There is already an object named  AboutUs  in the database     at System Data SqlClient SqlConnection OnError SqlException exception  Boolean breakConnection  Action 1 wrapCloseInAction     at System Data SqlClient SqlInternalConnection OnError SqlException exception  Boolean breakConnection  Action 1 wrapCloseInAction     at System Data SqlClient TdsParser ThrowExceptionAndWarning TdsParserStateObject stateObj  Boolean callerHasConnectionLock  Boolean asyncClose     at System Data SqlClient TdsParser TryRun RunBehavior runBehavior  SqlCommand cmdHandler  SqlDataReader dataStream  BulkCopySimpleResultSet bulkCopyHandler  TdsParserStateObject stateObj  Boolean amp  dataReady     at System Data SqlClient SqlCommand RunExecuteNonQueryTds String methodName  Boolean async  Int32 timeout  Boolean asyncWrite     at System Data SqlClient SqlCommand InternalExecuteNonQuery TaskCompletionSource 1 completion  String methodName  Boolean sendToPipe  Int32 timeout  Boolean asyncWrite     at System Data SqlClient SqlCommand ExecuteNonQuery      at System Data Entity Infrastructure Interception DbCommandDispatcher  lt NonQuery gt b  0 DbCommand t  DbCommandInterceptionContext 1 c     at System Data Entity Infrastructure Interception InternalDispatcher 1 Dispatch TTarget TInterceptionContext TResult  TTarget target  Func 3 operation  TInterceptionContext interceptionContext  Action 3 executing  Action 3 executed     at System Data Entity Infrastructure Interception DbCommandDispatcher NonQuery DbCommand command  DbCommandInterceptionContext interceptionContext     at System Data Entity Internal InterceptableDbCommand ExecuteNonQuery      at System Data Entity Migrations DbMigrator ExecuteSql DbTransaction transaction  MigrationStatement migrationStatement  DbInterceptionContext interceptionContext     at System Data Entity Migrations Infrastructure MigratorLoggingDecorator ExecuteSql DbTransaction transaction  MigrationStatement migrationStatement  DbInterceptionContext interceptionContext     at System Data Entity Migrations DbMigrator ExecuteStatementsInternal IEnumerable 1 migrationStatements  DbTransaction transaction  DbInterceptionContext interceptionContext     at System Data Entity Migrations DbMigrator ExecuteStatementsInternal IEnumerable 1 migrationStatements  DbConnection connection     at System Data Entity Migrations DbMigrator  lt  gt c  DisplayClass30  lt ExecuteStatements gt b  2e      at System Data Entity SqlServer DefaultSqlExecutionStrategy  lt  gt c  DisplayClass1  lt Execute gt b  0      at System Data Entity SqlServer DefaultSqlExecutionStrategy Execute TResult  Func 1 operation     at System Data Entity SqlServer DefaultSqlExecutionStrategy Execute Action operation     at System Data Entity Migrations DbMigrator ExecuteStatements IEnumerable 1 migrationStatements  DbTransaction existingTransaction     at System Data Entity Migrations DbMigrator ExecuteStatements IEnumerable 1 migrationStatements     at System Data Entity Migrations Infrastructure MigratorBase ExecuteStatements IEnumerable 1 migrationStatements     at System Data Entity Migrations DbMigrator ExecuteOperations String migrationId  XDocument targetModel  IEnumerable 1 operations  IEnumerable 1 systemOperations  Boolean downgrading  Boolean auto     at System Data Entity Migrations DbMigrator AutoMigrate String migrationId  VersionedModel sourceModel  VersionedModel targetModel  Boolean downgrading     at System Data Entity Migrations Infrastructure MigratorLoggingDecorator AutoMigrate String migrationId  VersionedModel sourceModel  VersionedModel targetModel  Boolean downgrading     at System Data Entity Migrations DbMigrator Upgrade IEnumerable 1 pendingMigrations  String targetMigrationId  String lastMigrationId     at System Data Entity Migrations Infrastructure MigratorLoggingDecorator Upgrade IEnumerable 1 pendingMigrations  String targetMigrationId  String lastMigrationId     at System Data Entity Migrations DbMigrator UpdateInternal String targetMigration     at System Data Entity Migrations DbMigrator  lt  gt c  DisplayClassc  lt Update gt b  b      at System Data Entity Migrations DbMigrator EnsureDatabaseExists Action mustSucceedToKeepDatabase     at System Data Entity Migrations Infrastructure MigratorBase EnsureDatabaseExists Action mustSucceedToKeepDatabase     at System Data Entity Migrations DbMigrator Update String targetMigration     at System Data Entity Migrations Infrastructure MigratorBase Update String targetMigration     at System Data Entity Migrations Design ToolingFacade UpdateRunner Run      at System AppDomain DoCallBack CrossAppDomainDelegate callBackDelegate     at System AppDomain DoCallBack CrossAppDomainDelegate callBackDelegate     at System Data Entity Migrations Design ToolingFacade Run BaseRunner runner     at System Data Entity Migrations Design ToolingFacade Update String targetMigration  Boolean force     at System Data Entity Migrations UpdateDatabaseCommand  lt  gt c  DisplayClass2  lt  ctor gt b  0      at System Data Entity Migrations MigrationsDomainCommand Execute Action command  ClientConnectionId 88b66414-8776-45cd-a211-e81b2711c94b There is already an object named  AboutUs  in the database  PM gt

User · Answer

Another way to do that is comment everything in Initial Class between Up and Down Methods Then run update-database  after running seed method was successful so run update-database again It maybe helpful to some friends

User · Answer

I had the same issue described in the answer that Elnaz gave   I had a requirement to change the namespace of the datalayer during a refactoring of our project   This caused the migrations to not see the existing migrations in the database  I found an excellent answer to this issue that James Chambers blogged   http   jameschambers com 2014 02 changing-the-namespace-with-entity-framework-6-0-code-first-databases   I simply changed the following in the Migration configuration file   public Configuration         AutomaticMigrationsEnabled   false      this ContextKey      Old Namespace Migrations Configuration         Hope this helps someone else in a bind

User · Answer

In my case  my EFMigrationsHistory table was emptied  somehow  and when trying to run update-database I would get       There is already an object named  AspNetUsers  in the database   After seeing the table had been emptied it made sense that it was trying to rerun the initial migration and trying to recreate the tables   To fix this problem I added rows into my EFMigrationsHistory table  1 row for each migration that I knew the database was up to date with   A row will have 2 columns  MigrationId and ProductVersion  MigrationId is the name of your migration file  Example  20170628112345 Initial  ProductVersion is the ef version you re running  You can find this by typing Get-Package into the Package Manager Console and looking for your ef package   Hope this is helpful for someone

User · Answer

Make sure your solutions startup project has the correct connectionstring in the config file  Or set the -StartUpProjectName parameter when executing the update-database command  The -StartUpProjectName parameter specifies the configuration file to use for named connection strings  If omitted  the specified project   s configuration file is used     Here is a link for ef-migration command references http   coding abel nu 2012 03 ef-migrations-command-reference

User · Answer

I was facing the same issue  I tried below solution   1  deleted create table code from Up   and related code from Down   method 2  Run update-database command in Package Manager Consol  this solved my problem

User · Answer

There is already an object named  AboutUs  in the database     This exception tells you that somebody has added an object named  AboutUs  to the database already    AutomaticMigrationsEnabled   true  can lead to it since data base versions are not controlled by you in this case  In order to avoid unpredictable migrations and make sure that every developer on the team works with the same data base structure I suggest you set AutomaticMigrationsEnabled   false    Automatic migrations and Coded migrations can live alongside if you are very careful and the only one developer on a project   There is a quote from Automatic Code First Migrations post on Data Developer Center      Automatic Migrations allows you to use Code First Migrations without   having a code file in your project for each change you make  Not all   changes can be applied automatically - for example column renames   require the use of a code-based migration       Recommendation for Team Environments      You can intersperse automatic and code-based migrations but this is   not recommended in team development scenarios  If you are part of a   team of developers that use source control you should either use   purely automatic migrations or purely code-based migrations  Given the   limitations of automatic migrations we recommend using code-based   migrations in team environments

User · Answer

I had same problem and after three hour struggling I find out what s going on  In my case  when I wanted to migrate for the first time in up   method  the default code wants to create the tables that already existed so I got same error as you  To solve it  just delete those code and write want you want  For example  I wanted to add a column so i just write  migrationBuilder AddColumn lt string gt               name   fieldName               table   tableName               nullable  true

User · Answer

Note  I did it because I don t have anything in my database   In my case   1  I removed a migration by command remove-migration in Package Manager Console   2  Removed database by  SQL Server Object Explorer  panel   on current database   right-click   Remove  3  Migrated in Package Manager Console write Add-Migration and click Enter  4  The last update by command update-database

User · Answer

Same case  no DB and MigrationHistory table on Server   My steps    I deleted Migration data from Up and Down section of my first migration   Update Database with empty migration  MigrationHistory table was created  Add your REAL migration and update database with it

User · Answer

Another edge-case EF Core scenario   Check you have a Migrations YOURNAMEContextModelSnapshot cs file   as detailed in - https   docs microsoft com en-us ef core managing-schemas migrations  create-a-migration  If you have tried to manually re-create your database by deleting migration cs files  be careful that your Migrations  ContextModelSnapshot cs file still exists   Without it  your subsequent migrations have no snapshot on which to create the required differences and your new migrations files will look like they are re-creating everything again from scratch  you will then get the existing table error as above

User · Answer

Note  not recommended solution  but quick fix in some cases   For me  dbo  MigrationHistory in production database missed migration records during publish process  but development database had all migration records   If you are sure that production db has same-and-newest schema compared to dev db  copying all migration records to production db could resolve the issue   You can do with VisualStudio solely    Open  SQL Server Object Explorer  panel   right-click dbo  MigrationHistory table in source in my case dev db  database   Click  Data Comparison     menu  Then  Data Comparison wizard poped up  select target database in my case production db  and click Next  A few seconds later  it will show some records only in source database  just click  Update Target  button  In browser  hit refresh button and see the error message gone    Note that  again  it is not recommended in complex and serious project  Use this only you have problem during ASP Net or EntityFramework learning

User · Answer

In my case  the issue was in Seeder  I was calling  ctx Database EnsureCreated   inside of it and as far as I understood  the update database command has successfully executed  but then seeder tried to create database  second  time   How to address    Do nut run update  just start application and call EnsureCreated    Database will be created updated Comment out or remove seeder

User · Answer

You have deleted migration folder than you are trying to run  update-database  command on Package manager console   if so  Just manually delete all you tables Than run if update-databse cons seed data will be deleted

User · Answer

In migration file check the public override void Up   method  May be you are trying to create a new db object which is already in database   So  you need to drop this object table before creation of the db object  Just do like bellow-  DropTable  dbo ABC     CreateTable               dbo ABC               c   gt  new                                       Id   c Int nullable  false  identity  true                                               And now run your migration       Update-Database -TargetMigration   2016 YourMigration

User · Answer

same happened with me   Problem was that Actually i deleted my Database table MoviesCast and made new table and problem was that my last migration was trying to induce the deleted table MoviesCast in the database  I Solved it by simply removing all the content of last migration and simply ran Up    amp  down   method   public override void Up        public override void Down         then updated the database and simply add new migration

User · Answer

The below steps worked for me for the same issue  Scenario  I was trying to add 2 new fields to my existing model for Email functionality  The new fields are  quot IsEmailVerified quot  and  quot ActivationCode quot  Steps i have followed  1 Deleted old migration files under  quot Migrations quot  folder which are prevented me to do Update-Database 2 Reverted all my recent changes that i have did on the model 3 Run the below command  Add-Migration  -ConnectionProviderName System Data SqlClient -ConnectionString  quot Data Source DESKTOP SQLEXPRESS Initial Catalog Custom Persist Security Info True User ID sa password      quot  4 Deleted the contents from Up   and Down   methods from migration file and left the methods empty 5 Run the below command  Update-Database -ConnectionProviderName System Data SqlClient -ConnectionString  quot Data Source DESKTOP SQLEXPRESS Initial Catalog Custom Persist Security Info True User ID sa password  quot      After executes the above step  model and DB looks sync   Now  i added the new properties in the model      public bool IsEmailVerified   get  set         public Guid ActivationCode   get  set      Run the below command    Add-Migration  -ConnectionProviderName System Data SqlClient -ConnectionString  quot Data Source DESKTOP SQLEXPRESS Initial Catalog Custom Persist Security Info True User ID sa password  quot      Now the migration file contains only my recent changes as below     public override void Up                   AddColumn  quot dbo UserAccounts quot    quot IsEmailVerified quot   c   gt  c Boolean nullable  false             AddColumn  quot dbo UserAccounts quot    quot ActivationCode quot   c   gt  c Guid nullable  false                        public override void Down                   DropColumn  quot dbo UserAccounts quot    quot ActivationCode quot             DropColumn  quot dbo UserAccounts quot    quot IsEmailVerified quot             Run the below command  Update-Database -ConnectionProviderName System Data SqlClient -ConnectionString  quot Data Source DESKTOP SQLEXPRESS Initial Catalog Custom Persist Security Info True User ID sa password  quot       11 Now i successfully updated the database with additional columns  The below is updated table after the recent changes  Table after the update migration

User · Answer

Delete rows from dbo MigrationHistory table or delete the table and run  update-database -verbose   It will run all the migrations in your project one by one

User · Answer

After more than an hour of not getting any results I tried another approach  not using migrations but I did a schema compare   In Visual Studio -  Tools -  SQL Server -  New Schema Comparison  First I created a new completely new database with EF migrations  Than I did a compare  comparing the new database with the one I wanted to update  Finally generated a migration script  and I could perform a schema update

User · Answer

Maybe you have changed the namespace in your project  There is a table in your data base called dbo   MigrationHistory  The table has a column called ContextKey  The value of this column is based on your namespace  for example is  DataAccess Migrations Configuration   When you change the namespace  it causes duplicate table names with different namespaces  So  after you change namespace in code side  change the namespace in this table in database  too   for all rows   For example  if you change the namespace to EFDataAccess  then you should change the values of ContextKey column in dbo   MigrationHistory to  EFDataAccess Migrations Configuration   Then in code side  in Tools    Package Manager Console  use the update-database command   Another option instead of changing the context value in the database is to hard code the context value in your code to the old namespace value  This is possible by inheriting DbMigrationsConfiguration lt YourDbContext gt  and in the constructor just assign the old context value to ContextKey  than inherit from MigrateDatabaseToLatestVersion lt YourDbContext  YourDbMigrationConfiguration gt  and leave that class empty  The last thing to do is call Database SetInitializer new YourDbInitializer     in your DbContext in a static constructor   I hope your problem will be fixed

User · Answer

In my case  want to reset and get a fresh database     First I has got the error message    There is already an object named  TABLENAME  in the database   and I saw  a little bit before    Applying migration  20111111111111 InitialCreate   Failed executing DbCommand  16ms   Parameters     CommandType  Text   CommandTimeout  30   CREATE TABLE MYFIRSTTABLENAME    My database was created  but no record in migrations history   I drop all tables except dbo   MigrationsHistory  MigrationsHistory was empty   Run  dotnet ef database update -c StudyContext --verbose   --verbose just for fun   and got Done

User · Answer

In the database  query   MigrationHistory table and copy  ContextKey    Paste it into the DbMigrationsConfiguration ConextKey as below  internal sealed class DbConfiguration  DbMigrationsConfiguration lt DbContext gt                public DbConfiguration                         AutomaticMigrationsEnabled   true              ContextKey     lt contextKey from above gt

User · Answer

Simply execute command update-migration -Script  This generate new   sql script which include all DB changes included in migration  In the end of code are insert commands something like this  INSERT  dbo     MigrationHistory   MigrationId    ContextKey    Model    ProductVersion   you can simply run this all INSERT and DB will be synchronized

User · Answer

I faced the same bug as below  Then I fixed it as below    Check current databases in your project    dotnet ef migrations list  If the newest is what you ve added  then remove it    dotnet ef migrations remove  Guarantee outputs of this database must be deteled in source code   cs  Designer cs files   4 Now it is fine  Try to re-add   dotnet ef migrations add  new dbo name   5 Finally  try to update again  in arrangement base on migration list    dotnet ef database update  First   dotnet ef database update  Second       dotnet ef database update  new dbo name    Hope it is helpful for you

User · Answer

In my case I had re-named the assembly that contained the code-first entity framework model  Although the actual schema hadn t changed at all the migrations table called  dbo   MigrationHistory   contains a list of already performed migrations based on the old assembly name  I updated the old name in the migrations table to match the new and the migration then worked again

User · Answer

it seems there is a problem in migration process  run add-migration command in  Package Manager Console       Add-Migration Initial -IgnoreChanges   do some changes  and then update database from  Initial  file      Update-Database -verbose   Edit  -IgnoreChanges is in EF6 but not in EF Core  here s a workaround  https   stackoverflow com a 43687656 495455

[database] There is already an object named in the database

Examples related to database

Examples related to entity-framework

Examples related to ef-code-first

Examples related to entity-framework-6

Examples related to entity-framework-migrations