Skip to main content
17 events
when toggle format what by license comment
May 10, 2013 at 12:30 audit Close votes
May 10, 2013 at 13:11
May 8, 2013 at 22:06 audit Close votes
May 8, 2013 at 22:06
May 8, 2013 at 7:46 audit Close votes
May 8, 2013 at 13:16
Apr 25, 2013 at 14:05 answer added Arnab timeline score: 1
Apr 24, 2013 at 23:21 answer added Jeff Martin timeline score: 0
Apr 17, 2013 at 19:46 comment added jwatts1980 @kevin cline: transforming the data going into the database means it gets stored based on the computations used at that moment. Changing the calculation on the presentation side would affect all historical reports as well (unless additional steps were taken to separate the calculations). This too has pros and cons, but the decision has already been made to calculate prior to storage.
Apr 17, 2013 at 15:34 comment added kevin cline If the computations are simple, why not use one table and perform the computations when the report is generated? It seems you are denormalizing your database for little gain.
Apr 17, 2013 at 14:08 vote accept jwatts1980
Apr 17, 2013 at 13:47 comment added jwatts1980 See edit... I elaborated on the "2 db connections" comment
Apr 17, 2013 at 13:46 history edited jwatts1980 CC BY-SA 3.0
added 429 characters in body
Apr 17, 2013 at 5:21 comment added gnat see: Do stored procedures violate three-tier separation? and Database Application Design Best Practices
Apr 17, 2013 at 4:42 answer added Craig Tullis timeline score: 7
Apr 17, 2013 at 1:54 history tweeted twitter.com/#!/StackProgrammer/status/324340161070641152
Apr 17, 2013 at 0:03 answer added System Down timeline score: 10
Apr 16, 2013 at 23:58 comment added System Down Why would you need two database connections? The stored procedures can always share the same connection.
Apr 16, 2013 at 23:06 history edited user28988 CC BY-SA 3.0
Thanks are unnecessary. A nice thought but we're professionals.
Apr 16, 2013 at 22:41 history asked jwatts1980 CC BY-SA 3.0