ASP.NET Membership Database: Relationships and UniqueIdentifiers
Posted on 2009-05-01
I have created an ASP.NET application. I automatically configured membership with the built-in tools which stores all membership info in my app_data folder in a SQL express database.
Meanwhile, the rest of my data for my application is stored in a separate SQL Server database. Some fields in this database need to relate to the user table, but I can't build a relationship because the automatic configuration of the membership database sets the datatype of the UserID to UniqueIdentifier, thus I can't build a relationship.
My questions is:
1. Is this the best way to build this? Or should I have everything in one central database?
2. If this is an acceptable way to do this, how do I build the relationship?