Posted by Erland Sommarskog on 06/02/05 23:23

(martind-crap1@mailblocks.com) writes:
> The reason I'm using OO terminology instead of modeling the DB in
> purely relational terms is because i want to introduce a standardized
> object-relational mapping approach. I believe that although this
> introduces a bit more complexity upfront, it will save development time
> and costs in the long run...

I don't exactly what your plans are, but relational databases are
not that very object-oriented. Sure, some knowledge and experience
of object-oriented design can be an advantage, as far as it helps you
to recognize some patterns. But in the end, you should work in the
relational domain you are in. You might be able to save some development
time doing it your way - until you find that you have 20 GB and your
design does not scale.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

[Back to original message]