Yeah David, your right. I know nothing. I suppose the 2 years I made money
doing the rather boring work of being a DBA doesn't mean anything. Nor the
time I spent building a rather amazing database that would take a test, and
break it up into a dizzying array of tables. Plus all the statistical
analysis and Oracle Reports. Yeah. Ok.

What he wants to do is simple tracking. Simple. SIMPLE. What he stated he
wanted to do with the data does not really warrant all this normalization,
etc, etc. He did not state he wanted to do searches. Where did that come
from? The storage is going to be a moot point.

Read what you just said, look at his original post, and come to the
realization that you are proposing a beast of a system to do something he
didn't express the desire to do. What he wants to do can be accomplished
just fine flat file, index cards, or something else in addition too a
relational database. I just think unless there is going to be a lot of data
or he's going to be running queries (like I said in a previous post), then
there really isn't any need for it. It is not like his report about how many
3rd viola parts that are in the library, bought before 2007, published by
Schrimer, on oversized paper is ever going to be printed, read, or even
thought about.


On Tue, Aug 19, 2008 at 7:39 PM, David W. Fenton
<[EMAIL PROTECTED]>wrote:

> On 19 Aug 2008 at 19:21, Eric Dannewitz wrote:
>
> > I'm not going to argue that
> > a relational database isn't a good thing. It is. For huge amounts of
> > data.
>
> You really understand *nothing* about proper database design if you
> think the *amount* of data involved determines what the level of
> complexity of the data structure should be. The determinant is *what
> you want to do with the data*. Everything else is secondary.
>
> Properly normalized database design improves the accuracy and
> efficiency of the data storage, which in turn improves the accuracy
> and efficiency of searching the data. Yes, it means that UI is going
> to be somewhat more complex to build, but with easy-to-use tools like
> FileMaker, this is much less of an issue than it was in the days of
> dBase and the like.
>
> --
> David W. Fenton                    http://dfenton.com
> David Fenton Associates       http://dfenton.com/DFA/
>
> _______________________________________________
> Finale mailing list
> [email protected]
> http://lists.shsu.edu/mailman/listinfo/finale
>
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale

Reply via email to