Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Recommendation on a design issue
Message
From
19/02/2009 12:26:06
 
 
To
All
General information
Forum:
Microsoft SQL Server
Category:
Database design
Title:
Recommendation on a design issue
Environment versions
SQL Server:
SQL Server 2008
Application:
Web
Miscellaneous
Thread ID:
01382935
Message ID:
01382935
Views:
124
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?
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Next
Reply
Map
View

Click here to load this message in the networking platform