>Some important information is missing:
>Do all members have one or more choices?
>What's the average number of choices per member?
>If you want to find which choices are selected for a particular member then the single table might be faster. But if you need to determine which members have a specific selection of choices then the current setup might be quicker since you're presumably selecting from a much smaller table.

They can have multiple choices. The average would be two. The decision was to keep it as is. So, I kept the design which is relational and we'll see how it goes.