Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
key
Starting Member
2 Posts |
 Posted - 2008-01-15 : 01:30:43
|
| Hi all,I have to come up with a design choice for a DB Table for a financial firm(i.e. Tables with Fixed column or Value-Pair). SQL Server 2005 is used as a back-end for a web application(which basically is designed for doing web based analysis). The business people are insisting on a feature that enable power users to add fields to the underlying tables. One option proposed is named value-pair design approach? But from performance point of view, this seems a nightmare. How can this be integrated into static-column table approach. FYI, security policy of the client do not allow the underlying table structures to be changed by the user and currentlythere are 5000 fields, and growing...Thanks for your suggestions!!Dilla |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2008-01-15 : 03:05:25
|
| Check http://www.sqlmag.com/Articles/Inde...ArticleID=38656, which is one potential solution to what you are outlining. The method you are proposing , is difficult to query in the long runJack Vamvas--------------------Search IT jobs from multiple sources- http://www.ITjobfeed.com |
 |
|
|
|
|
|
URGENT HELP with Database Table Design!!