Results 1 to 2 of 2
  1. #1
    Join Date
    Oct 2014
    Posts
    1

    Are there performance benefits to keeping lightly used columns in a separate table?

    Let's say I have these two tables to track computer servers being provisioned with an operating system:

    Hardware
    hardwareID PK
    hardwareTypeID FK
    locationID FK
    serialNumber
    uuid

    HardwareType
    hardwareTypeID PK
    hardwareName
    manufacturer
    model


    Also, for a given hardwareType, I need to track tons of additional details like cpuCount, cpuType, cpuCores, cpuBusSpeed, memoryTotal, networkInterfaceType, networkInterfaceDescription, etc. But I do not expect to need to access this data often, probably only if someone wants to drill down into the specifics of different hardware types.

    Is there any value in having a separate HardwareDetails table, when in reality, all of these columns could be in the HardwareType table?

    Thanks in advance,

    --KarmicDebt

  2. #2
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    It depends on the database engine, but there is so little to be gained that I wouldn't bother.

    -PatP
    In theory, theory and practice are identical. In practice, theory and practice are unrelated.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •