Different database for Membership and our web data or use just one?

Posted by Jesus Rodriguez on Programmers See other posts from Programmers or by Jesus Rodriguez
Published on 2012-12-13T14:21:42Z Indexed on 2012/12/13 17:16 UTC
Read the original article Hit count: 430

Is better to keep our Membership stuff on the DefaultConnection and create another connection (another database) for our data? Or just one database for all?

If I have a MyAppContext and I want migrations for that context, It seems that I cannot have migrations for UserContext (In other words, I can just migrate one context)

So, having two different databases I can migrate or the users (maybe membership migration is weird) or the web data. Or, I can mix the UserContext and MyAppContext in one UserAndAppContext and migrate all in one place, but this mixing also seems weird.

What's the normal way to do this, one or two databases and what should be migrated?

© Programmers or respective owner

Related posts about asp.net-mvc

Related posts about entity-framework