Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. How to manage 1000 millions of record in Mysql database

How to manage 1000 millions of record in Mysql database

Scheduled Pinned Locked Moved Database
databasemysqltutorialquestion
3 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    Member 12069869
    wrote on last edited by
    #1

    I want to manage 10 major tables with 100 millions record each, each row have about 20 fields/colums, so how to manage these 10 interlinked tables. Can MySql handle such large data?

    L J 2 Replies Last reply
    0
    • M Member 12069869

      I want to manage 10 major tables with 100 millions record each, each row have about 20 fields/colums, so how to manage these 10 interlinked tables. Can MySql handle such large data?

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      See http://tagide.com/blog/advice/how-to-handle-large-data-in-mysql/[^].

      1 Reply Last reply
      0
      • M Member 12069869

        I want to manage 10 major tables with 100 millions record each, each row have about 20 fields/colums, so how to manage these 10 interlinked tables. Can MySql handle such large data?

        J Offline
        J Offline
        jschell
        wrote on last edited by
        #3

        Member 12069869 wrote:

        Can MySql handle such large data?

        Yes. Of course that doesn't mean your application can. Nor that you can't mess it up by failing to design correctly.

        Member 12069869 wrote:

        each row have about 20 fields/colums

        Things that matter - What is the maximum, average and variance for the row size (your data not db overhead.) - What is the realistic growth rate? Realistic means that, not pie in the sky sales/marketing claims. - What will the system be querying on most? Unless your growth rate is very big this is more relevant. - Can data be aged? Thus will the above queries be mostly for the last month, or last three months versus spanning the entire data store

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups