Tag Info

New answers tagged

2

I think saying "The only valid use is for staging tables used in import/export/ETL processes" is a little restrictive to say the least. You have to take a given system's expected use case and then choose based on the merits of heaps or index organised tables (I know, an Oracle term but it describes it nicely). Our warehouse loads ~1.5 billion rows a day and ...


3

Major Considerations I see one important advantage for heaps and one for clustered tables, plus a third consideration which can go either way. A heap saves you a layer of indirection. Indexes contain row IDs, pointing directly (well, not really, but as directly as possible) to a disk location. Thus, an index seek against a heap should cost roughly half ...


3

First I'm assuming that both ID and Type are INT columns. Second that this is going to be a somewhat active table with a fair number of inserts (and possibly deletes). And last but not least that you aren't going to be pulling a "range" of IDs. For example you don't need to look at ID 10000-15000. If so I would create a third column that is an INT ...



Top 50 recent answers are included