Inventory Handling

sabzam

Dear All,

What is the amount of items which is considered as decent for NAV to handle, as I had clients which would run into performance issues, after a couple of thousands.

Regards,

Steve

tinoruijs

The number of items present in a database is not important for performance.
What can affect performance is the number of sales/purchase-orderlines there are on an order or invoice and the setup of the items.
And how the inventory setup is (Automatic Cost Posting for example).
I've seen bad performance in databases where orders were not deleted and kept in the database. Be sure to delete them.

sabzam

Thanks

jubeljoy

Also recommended you to delete un-necessary table records(Change Log with less than 1 Month records delete etc.) and optimise keys. After doing this you can able see huge impact on the system perfromance

sabzam

Excellent thanks.

rico1931

jubeljoy wrote:

Also recommended you to delete un-necessary table records(Change Log with less than 1 Month records delete etc.) and optimise keys. After doing this you can able see huge impact on the system perfromance

Hi Jubeljoy,

So I have this problem where the company wants to keep certain table records in the change log for forever ](*,) but I'm curious to what you are saying about optimizing keys.... can you explain this a bit more and where it needs to be done? Is this a Nav thing? or I'm going to guess it's a SQL thing.

Thanks

tinoruijs

rico1931 wrote:

So I have this problem where the company wants to keep certain table records in the change log for forever ](*,)

No problem for performance when change log keeps growing.