On Fri, 2 Mar 2012 13:26:23 +1100, BareFeetWare
wrote:
> Hi Rich,
>
>> I wanted to solicit some opinions about how best to layout a database table
>> for a project I am working on. I have a distributed application that
>> reports run time information back to a
On 2 Mar 2012, at 3:44am, Mario Becroft wrote:
> Making schema changes, such as adding or removing attributes, is not
> necessarily difficult. This is what DML is for. However one thing SQL
> does not handle well is temporal schemas, i.e. ones in effect during
> different
I agree with what has been said so far regarding normalization, getting
the underlying structure right, and using views to access the data. I
would add a couple of points:
Database refactoring is not necessarily as hard as has been
suggested. In fact, a good design, separating data storage
Hi Rich,
> I wanted to solicit some opinions about how best to layout a database table
> for a project I am working on. I have a distributed application that reports
> run time information back to a central machine. Included in the report are
> the parameters used during runtime... approx 25
On Mar 2, 2012, at 1:28 AM, Rich Rattanni wrote:
> I realize design A may not be "best", but I would prefer an friendly
> answer and not a canned response like I get from co-workers.
[warning: canned answer ahead]
FWIW, there is some good wisdom in going down the "text book" way, aka
5 matches
Mail list logo