Multiple identity columns specified for table 'States'. Only one identity column per table is allowed

This post addresses the error that we see when executing Update-Database command inside Package Manager Console. I am going to talk about two continuous error appears and fix is very simple, just read this blog.

Error 1 - Here is the error I got inside Package Manager Console:

Multiple identity columns specified for table 'States'. Only one identity column per table is allowed.

I encountered this error when trying to execute ‘Update-Database’ command and the scaffolded migration script class [which has Up() and Down() methods] failed to arrange drop/add/create/rename job order.

Error 2 - If you again do ordering in a wrong way, you will see another error very similar to one given below.

The object 'PK_dbo.States' is dependent on column 'Key'.
ALTER TABLE DROP COLUMN Key failed because one or more objects access this column.

Now, to make this migration (scaffolded migration script class) work. We have to arrange jobs this way. In the image, green sign is a valid way and red sign is a wrong way.


I don’t know whether it is a template bug or I am doing things in a wrong way, if you know please share.

Hope this helps to one who getting this error.


Thanks for reading.

Comments

Post a Comment

Popular posts from this blog

Migrating database from ASP.NET Identity to ASP.NET Core Identity

Image
As you know ASP.NET Core Identity (table structure) is different from what we had earlier in ASP.NET Identity. Actually the identity system which we have today with .NET Core is very mature and continuously evolved be it ASP.NET Membership, ASP.NET Identity 1, ASP.NET Identity 2 and now ASP.NET Core Identity. Recently I had to migrate few application to ASP.NET Core and similar its identity database. Because the table schema is changed, i had to re-think and create migration script which I would like to share with you today. It is very simple and easy, just three step and I had everything ready: STEP 1 : Change name of existing tables STEP 2 : Create ASP.NET Core Identity tables STEP 3 : Migrate data from old tables (ASP.NET Identity) to new tables (ASP.NET Core Identity) Script:  https://gist.github.com/itorian/c699e8534b392a6c726ec66c48100072 You should also watch my video, where I demoed migration.
Read More »

Customize User's Profile in ASP.NET Identity System

Image
Note: You should read this post instead, I found below walkthrough will not work on ASP.NET Identity 2. I will re-work on this post soon. In this post you will learn how to customize User’s Profile and add some more fields like FirstName, LastName, EmailID etc with ASP.NET Identity System. In my last post I listed some of the great new features introduced with Identity system .
Read More »

Lambda two tables and three tables inner join code samples

In this blog post you will learn inner join using lambda queries. There will be two samples, in first sample you will see how you can join two tables and in second sample you will see how you can extend even further to join three tables and so on. I will sample in-memory data, but the same implementation will work with IQueryable (lazy query) too. Here's the code snippet:- namespace ConsoleApp1 {     class Program     {         static void Main()         {             var table1 = new List<Table1>();             table1.Add( new Table1 { Id = 1, Name = "Name 1" , Address = "Address 1" });             table1.Add( new Table1 { Id = 2, Name = "Name 2" , Address = "Address 2" });             table1.Add( new Table1 { Id = 3, Name = "Name 3" , Address = "Address 3" });             table1.Add( new Table1 { Id = 4, Name = "Name 4" , Address = "Address 4" });   
Read More »