Estimate the size of records-database

elmaelma Member Posts: 12
edited 2004-01-14 in Navision Attain
Dear friends!

We were looking for some kind of case study regarding the size of records, some estimations e.g. when a customer needs database with app. 500.000 records per year, which size of database can be expected.

Actually, our potential customer of Navision wants to know possibilities of Navision db (we know the limit 64 GB), and for how long he can be satisfied with Navision db, and when (considering this rhythm od records 500.000/year) he would need migration to SQL database.

(they do print and post of invoices-app. 500.000/year-tables: Sales (Invoice) Header & Sales (Invoice) Line)



We have an idea to do this alone, but we think that someone did it already.
Thanks in advance,

Elma Cigic
elma.cigic@bbs.ba


BBS d.o.o. Sarajevo
www.bbs.ba

Comments

  • eromeineromein Member Posts: 589
    Ok... Here is what I would do to make an indication. I'm not quite sure it's the best way, but better something then nothing.


    I would take a database of a customer with about the same activities. It's not important they have the same number of entries (records) per year, but the way they use Navision should be the same. What is very important is the period that this database has been used. The longer this database has been used, the more accurate the calculation will be.

    Then go to File/Database/Info/Table, (maybe optimize everything, but I would not suggest that)

    The copy and past everything to Excel. (You have to choose if you copy all companies or only the one that is most used)

    Then calculate the avg. Size per record by dividing the Size (KB) by No. of Record.

    Then calculate the avg. record Size in this company by summing all the avg. Size per record values and divide by the number of tables in Excel.

    Recalculate this avg. this value to a specific period (day, month or year). This value is off course an avg. of record size in a specific period, you have to recalc. It to a year to be able to multiply it by 500.000

    Multiply it by 500.000 then you have the size in KB per year.

    Divide by 1024 to get the MBs


    You can get a more accurate calculation by not including setup tables and "static" tables in the calculation.
    "Real programmers don't comment their code.
    If it was hard to write, it should be hard to understand."
  • elmaelma Member Posts: 12
    Thanks for your suggestions, but we cannot get the real data form the customer's db. We have used the quazy records, paste them in some tables and estimated that 0,7-1 KB/record.

    But we think that is not precise enough, so we hoped that someone has the other way, or results of some other example.



    Anyway thanks a lot,
    best regards,
    Elma
Sign In or Register to comment.