So which is the biggest database you have worked with ?sheer volume is meaningless, unless you're a hardware salesman
what matters is complexity
my biggest was 115 tables that i designed mineselbst
:) :)|||"In every large program there is a small program screaming to get out."|||in every complex database there is a simple denormalized table screaming to get out|||sheer volume is meaningless,
:) :)
So what you're saying is, size doesn't matter ;)|||In a very large database, there is a full table scan waiting to ruin your day.|||By that count I have worked with about 310 tables at a time... and there is a table i like to call MasterBuster ... tblCodes in which all simple master tables are combined... about 35 odd|||ah yes, the One True Lookup Table (or OTLT as it is known)
many otherwise intelligent modellers have fallen victim to the evil OTLT|||ah yes, the One True Lookup Table (or OTLT as it is known)
many otherwise intelligent modellers have fallen victim to the evil OTLT
I believe one reason the OTLT approach surfaced was because some early DBMS's had a small limit on the number of joins in one statement. I remember writing SQL statements with a limit of 8 joins... easy to exceed with lookup tables.
I have quit OTLT's, cold turkey. It was almost as hard as giving up cigarrettes.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment