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 |
|
brandonl
Yak Posting Veteran
58 Posts |
Posted - 2004-09-18 : 17:12:20
|
| Another thread inspired me to write this question.Which is preferred? Should the application to the calculations-or should SQL? I've always done it with SQL (except where I could not), thinking that is better design.Which do you think is better?~BrandonL |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-09-18 : 19:38:39
|
| Depends on the situation.I prefer to do most things in sql but ifthe calculation is to do with presentation it should probably be done nearer the client.If you have a lyer in the application that handles entities then it could be done there.You just need to avoid having to write the same calculation in multiple places.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2004-09-19 : 01:50:04
|
| I put all the business rules in SQL (I don't have a middle layer).So in my opinion if the calculation is realted to a "business rule" then I would put it in SQL.Which is basically what Nigel said too!Kristen |
 |
|
|
|
|
|