4 replies
by alberto_neves Accepted solution
by tony hopkinson Accepted solution
with a large bucket of salt, but for tips, tricks and techniques, this site takes some beating.
by alberto_neves Accepted solution
by tony hopkinson Accepted solution
Basically this is optimisation. Optimise for X, and you lose some Y. You can't consider the database in isolation, the implementaion e.g. hardware and DBMS choice and most definbitley the uses and usage patterns gerenarlly have a far greater impact than say 6NF, even 3NF in some cases.
Add an index to speed up a selection, you slow every change to the indexed fields.
Populate it sparsely you use more space, compact it it's even slower.
No free lunches. If for isntance inserts of new values are infrequent, then you can afford the index. If it's getting hammered in say a high speed data collection system, may be not.
Best solution depends on what you are solving, and in alot of cases there isn't a right answer, just one that's less wrong at the moment.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending