>>We've had a general dispute in my team few years ago, on "each type of traff ic >into its table" vs "cram 'em into as few as possible, and try to have only o ne >if you can". Since I'm the chief developer here, the other approach is taken - >having more tables gives you more trouble in maintenance and reporting. > >I used to do this, Dragan, but switched to the 'every little table' after hav in >g trouble with SQL-Select code and reports that needed to use the same table fo >r 3+ lookups. Lookup tables are another matter - and I do keep them separately; very often, the same lookup table is common to more apps, so having them separately adds to flexibility. What I meant is _traffic_, so if it's a warehouse, I don't need separate tables for things stuffed into it, and things taken out. All the warehouse's traffic is in one table, so if I need some item's history, it's in one place.