ASP.NET MVC Membership DB must be merged with site DB?

I am pla开发者_如何学编程nning to use ASP.NET MVC2 implemented membership system to manage users. Database that uses application should have tables that are related with these users. Is it possible to use two different databases and make relationships (foreign keys) between them or I will have to merge these two databases into one?

Thanks,

Ile

It is NOT possible to put up relationships between databases. You CAN use triggers to ensure relational integrity.

Otherwise I would say: all in one database, put them into different schemata.

I would put membership/roles in a separate database. I don't think having foreign key constraints is that useful. Its better decoupling if you go through the membership API rather than join with the tables directly. The only thing in the membership database you might need to look up often is the username. If thats becomes a performance problem I'd probably just create an lookup table, either in memory or in a lookup table in the other component's database.