>I have a design issue which I am considering. I have a pivot table which will contains 6 entries. At first, I did that as I did for all other applications, such as creating a pivot table. So, basically, my member table can be related to one or more entries in that table into a one to many relationship table. So, this means, whenever I want to locate member records based on that pivot table, I have to use a join case. This design is good for as long as that table may vary, such as adding more records such as a 7th one, a 8th one and so on. But, in my case, this will be fixed. So, in order to optimize the queries, I have thought of simply adding six fields in my member table and gain more performance when I will need that type of queries. Because, for that content, this will be searched heavily. So, I thought about simply adding those fields in my member table.
>
>Any thoughts?

Can you please re-phrase your question to make it clearer?

For now I can only answer in general, that sometimes de-normalizing the database is a good thing and will get a performance boost.