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 |
|
sillylady
Starting Member
13 Posts |
 Posted - 2007-11-12 : 01:18:45
|
| Hi All,I am desigining a table which will holds information of companies Balancesheet, IncomeStatements and Profit&Loss A/c. There will be certain fields which holds the simple or complex calculated results of several fields. My question is should I have a fields which will holds data of calculated fields or not? Those calculated fields can be used to calculate ratios. If I don't have those calculated fields in table then during ratio generation I will have to calculate those fields which may be complex.Any help?Thanks |
|
|
anonymous1
Posting Yak Master
185 Posts |
Posted - 2007-11-12 : 10:42:43
|
| calculated fields are useful as a single location to encapsulate code, it sounds like a good choice from the details you provided. if "select *" queries are typical, then maybe a view for encapsulation would be better. hope that helps. |
 |
|
|
|
|
|
Should a table have result of calculated fields?