DataBase Size...

Mehdi.Chahed
Mehdi.Chahed Member Posts: 14
edited 2006-01-23 in Navision Attain
Hi,

The company I'm workin for is using SQL Navision + Infostore (POS Management) for Retail.
This Add-on transfroms all sale tickets taken from tills into Sale Orders, then Posts them creating an Invoice and a Posted Shipment.
No need to talk about the size of the database. let's just say that it's HUGE!

We are actually looking to copress previous Accounting periods (Item Legger Entries - for the moment) and I'm looking for know case storie similar to our'?

...
Thanks!
Mehdi CHAHED
Email: mehdi.chahed@dufry.com.tn
DUFRY TUNISIA

Comments

  • ara3n
    ara3n Member Posts: 9,258
    Make sure no Item ledger entries are open. Make they are all fully invoiced. Make sure you've run adjust cost routine, and have posted it to GL.
    Make sure you don't need the data for any reporting.

    Also once you've run the the routine, run test db on item ledger and any tables that relate to Item ledger.
    MS does not recomend running compress routine. I would run it in test environment. I would do a back just in case the data is needed.

    Also if you upgrade, the upgrade routines sometimes choke.


    Otherwise good luck.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • Captain_DX4
    Captain_DX4 Member Posts: 230
    Depending on how customized your database is, it will imact on the ability to do Date Compression at all. Client I'm at has a very customized ledger, and they haven't been able to run it at all. Currently, they are at 88GB on the Native database format. You can still run, but it does tend to hurt performance over time.

    They key is to do rigourous testing in a backup system and get it validated by the financial team before performing it live!
    Kristopher Webb
    Microsoft Dynamics NAV Developer

Categories