Results 1 to 3 of 3
  1. #1
    Join Date
    Aug 2016

    Lightbulb Unanswered: Too many entries in the database

    My english is really poor i think so be lenient.

    I have a little probeme with my database. i already have a database that have one table with too match entries in the day, like 10000 entries. the entries are done by range. like when a user get article, every article have one identifier. the identifier are successive, so to save all the article, the user must just select the range (from 1920 to 2550) and all the article are save. in futur use we can select like article 2015 or 2016 to 2020.
    the articles are not save by range like one row but each article is one row in the database. It end with too many entries in one day.

    My question is, there is another way to do so? a best practice to manage so many entries? i would like to simply save a one rows like a range of articles but the problem is how can use the article afta because i will not just gat all the range but some part of the range only, i can destroy an article or give it to another user so and so one.

    I hope i explain my situation correctly. if not i will add more informations. My english is really poor i think so ....

    Thks a lot.

  2. #2
    Join Date
    Mar 2015
    Provided Answers: 4
    You really don't have a excess amount of entries. I have databases with well over 182 million records. I don't know your level of experience but best practices:
    1. Normalize databases. Rows that contain repeated value should be places in a separate table. For instance my data has jobs which have 3milion detail records. rather than keep job information on all three million records I created a jobs table with Job Number, begin date, and any other information that is common to all the detail records in the jobs. I then create a relationship between the Jobs table and the Detail table. Very fast and reduces the size of the database.
    2. Create indexes. However you access you data create a Index on that field. In my case this means that when I report on detail records outside of by job number which is the primary key, like by date, or operation, I have a index. If you are experiencing slow speeds try creating index's.
    There are many ways to optimize you database but these are the two most important.
    Last edited by wjburke2; 08-25-16 at 13:02.

  3. #3
    Join Date
    Aug 2016
    I really thanks you for your reply. I don't have much experience so your help is very important.

Posting Permissions

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