Why SQL Membership Database tables created by aspnet_regsql have no primary keys

Question

This question is about the tables created by aspnet_regsql for the ASP.NET 2.0 Membership database.

I am incorporating these tables and procs, etc from the database into my application database for ease of manageemnt and integration with the application data.

I notice that none of the tables have primary keys. This is a difficulty with the tools I use to create and manage entities, dto's, repository classes and validation.

Does anyone know why these tables do not have primary keys and whether adding primary keys to these tables will interfere with the operation of the baked-in stored procs that this database includes?

Thanks,

Kimball

Glorfindel · Accepted Answer · 2019-05-13 04:06:12Z

2

Then something must have gone wrong with your installation - in my case, all the tables in "aspnetdb" have primary keys like any serious table should have:

Try removing aspnetdb and reinstalling...

Marc

edited May 13, 2019 at 4:06

Glorfindel

22.8k13 gold badges97 silver badges124 bronze badges

answered Nov 28, 2009 at 12:11

marc_s

760k186 gold badges1.4k silver badges1.5k bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Why SQL Membership Database tables created by aspnet_regsql have no primary keys

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related