How Many Rows?

Discussion in 'Databases' started by sundaybrew, Feb 14, 2013.

0
  1. #1
    I HAVE searched the web, but the answers, I am finding are conflicting :)

    I am wondering if someone here can help me,

    What is the max rows mysql can hold?

    Thanks in advance,
     
    Solved! View solution.
    sundaybrew, Feb 14, 2013 IP
  2. diawilliam

    diawilliam Peon

    Messages:
    7
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    1
    #2
    There is no such limit on rows until and unless you exceed hardware capacity.
     
    diawilliam, Feb 14, 2013 IP
  3. digitalpoint

    digitalpoint Overlord of no one Staff

    Messages:
    38,334
    Likes Received:
    2,613
    Best Answers:
    462
    Trophy Points:
    710
    Digital Goods:
    29
    #3
    If you are using a 32-bit primary key on the table, you are just limited to a 32-bit number as far as number of records... 4,294,967,296 (but then you can use a 64-bit number instead).

    Now would you always WANT to have billions of records in a table? Probably not in most cases... what are you trying to do exactly?
     
    digitalpoint, Feb 14, 2013 IP
    sundaybrew likes this.
  4. sundaybrew

    sundaybrew Numerati

    Messages:
    7,294
    Likes Received:
    1,260
    Best Answers:
    0
    Trophy Points:
    560
    #4

    Shawn,

    Thanks for the information:

    I want to build a database of EVERY USA household psychical address, so I think we have 300 million + homes in the USA and growing......

    Would this be possible?
     
    sundaybrew, Feb 15, 2013 IP
  5. #5
    Yeah... Should be no issues there.
     
    digitalpoint, Feb 15, 2013 IP
    sundaybrew likes this.
  6. sundaybrew

    sundaybrew Numerati

    Messages:
    7,294
    Likes Received:
    1,260
    Best Answers:
    0
    Trophy Points:
    560
    #6
    Thanks so much for the rapid replies :)
     
    sundaybrew, Feb 15, 2013 IP
  7. digitalpoint

    digitalpoint Overlord of no one Staff

    Messages:
    38,334
    Likes Received:
    2,613
    Best Answers:
    462
    Trophy Points:
    710
    Digital Goods:
    29
    #7
    Also, searching and storing/retrieving are two different things. If the data is going to be searchable, I'd look at something like Sphinx or Elastic Search for the search part.
     
    digitalpoint, Feb 15, 2013 IP
    sundaybrew likes this.
  8. sundaybrew

    sundaybrew Numerati

    Messages:
    7,294
    Likes Received:
    1,260
    Best Answers:
    0
    Trophy Points:
    560
    #8
    Thanks so much for your feedback.

    Yes, its going to be 350 million "records" and be searchable.....

    Anything else that I should be concerned about?
     
    sundaybrew, Feb 16, 2013 IP
  9. digitalpoint

    digitalpoint Overlord of no one Staff

    Messages:
    38,334
    Likes Received:
    2,613
    Best Answers:
    462
    Trophy Points:
    710
    Digital Goods:
    29
    #9
    That's basically it for backend stuff.... storage/retrieval with MySQL and searching with a search engine. :)
     
    digitalpoint, Feb 16, 2013 IP
  10. Rukbat

    Rukbat Well-Known Member

    Messages:
    2,908
    Likes Received:
    37
    Best Answers:
    51
    Trophy Points:
    125
    #10
    You should be concerned about the fact that you're shooting at a moving target, and the data thruput is probably going to be a lot slower than your target.

    (IOW, enough people move often enough, and the data you get comes in delayed enough, that your database will probably always be WAY out of date.)
     
    Rukbat, Feb 16, 2013 IP