For normalization practices, you should put all profiles for a specific user id in a separate table called "Profile".
UserID - PK
ProfileID - PK
UserID - FK
With the setup above, you allow for data to be consistent and not redundant. If you put all possible profile options into one table, you are going to end up with one table that has multiple fields that may or may not be used - this will just take up space. If you create both tables separately, you can easily query them to find all profiles for an individual user.
SQL Server DBA/Developer
Web/Desktop Application Developer
Unicorn Financial Services/Contractor For Hire