Building the optimal user database model for your application In the past, I've often wrestled with designing an optimal relational database model to represent users in a multi-tenant system. I've wanted to get the model just right---enough structure to accomodate future enhancements without bloating the schema with excessive JOINs, overly-wide tables, or any other number of typical relational-dat