If i use a separated ASP.NET Membership database what is the correct way to define the relations between the user tables and application data tables?. Should i create copies of the user tables and sync? or is ok to just create the Guid columns and enforce validation in the application code?, Are there any issues with performance that i should be aware of when separating databases?
views:
73answers:
1
A:
I'm not sure I fully understand the question... Do you mean have the asp.net membership in it's own database .... IMO it's easier to integrate the database in the application database
Use the GUID PK from aspnet_membership as your FK in your related application table
Stuart
2009-06-30 04:56:54
He's asking how should he link the membership tables to his own custom tables. What should he use as the foreign keys.
AndyMcKenna
2009-06-30 04:59:29