I am designing a database for a potentially large data warehouse. Several of the fact tables may contain over a hundred columns. Some of these columns may be sparse since data extracted from various sources may have different attribute. We are debating between
1) Keep all columns and deal with sparseness. A few colleagues of mine worried about tables being sparse, but I don't see any problem with it. Perhaps I misses some important thing here. Would the width (number of columns) of a table have any impact on performance that much?
2) Move sparse columns into an EAV table. Queries will be more expensive, but how much more? Would you use this model in your own data warehouse?
I am not familiar enough with datawarehouse performance and think I would post this question ot the gurus in this community.
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…
Planning to migrate your EDB file(s) to a new or an existing Outlook PST file?
This video will guide you how to convert EDB file(s) to PST. Besides this, it also describes, how one can easily search any item(s) from multiple folders or mailboxes…