•  

Announcement

Announcement Module
Collapse
No announcement yet.

Is there a performance penalty when column in fact table different size then dimension table?

Page Title Module
Move Remove Collapse
Conversation Detail Module
Collapse
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts

  • Is there a performance penalty when column in fact table different size then dimension table?

    #1
    Have several very large fact tables (100+ million rows).

    In doing some maintainence on one of these fact tables, I can
    squish the size of several of my dimension keys from int to smallint.

    Don't want to touch the other fact tables at this point in time.

    Is there a performance penalty to having a dimension key in the fact table be
    of size smallint but still be of size int in the dimension table when a join
    is done?

    Thanks,

    Mike
    Tags: None
  • #2
    mikec wrote on Fri, 28 September 2007 04:32


    Is there a performance penalty to having a dimension key in the fact table be
    of size smallint but still be of size int in the dimension table when a join


    Generally yes, because you are forcing MySQL to perform an implicit data conversion on all records involved in the join.
    The question in this case is if the extra CPU cycles outweigh the smaller table size and resulting less reads from disk.

    My guestimation is that it doesn't so I would stick with same type on both columns involved with the join.

    Comment

    • #3
      Thanks, I'll do that

      Comment

      Working...
      X