Undo Sales Shipment Poor Performance

Jonathan2708

Hi,

We have a customer running Navision 4.00SP1 objects with 4.00SP3 clients on SQL Server 2005 and generally everything runs fine other than when users attempt to undo shipments. Whenever a person uses the undo shipment facility it performs it extremely slowly and slows/locks other users in the system.

This is the only function that causes problems. Does anybody know of any updates for this function or any tips on improving things in this area? The server is very new, Windows 2003 with 4GB memory, 2 processors and lots of disc space.

Any help appreciated,

Jonathan

Waldo

Has there been customizations made to this functionality?
afaik, there are no upgradations in this area ... but to be sure, you can use the code coverage and a compare tool to check... :-k .

I probably don't have to go into the "you should consider tuning SQL" ... do I?

Can you use SQL Profiler (or client monitor) to analyse the function, and see which SQL statement(s) causes the delay? May be a simple index-update on a certain table can do the trick ...

Jonathan2708

Hi,

Thanks for the reply. No there's no customisations in this area. Yes I've read about the need to tune SQL but didn't think it would be so necessary on such a standard piece of functionality.

My next step was going to be to step through the procedure line by line, also using SQL Profiler to track down the bottleneck.

Jonathan

Savatage

Jonathan2708 wrote:

My next step was going to be to step through the procedure line by line, also using SQL Profiler to track down the bottleneck.

Let the fun begin :^o

Waldo

Jonathan2708 wrote:

Hi,

Thanks for the reply. No there's no customisations in this area. Yes I've read about the need to tune SQL but didn't think it would be so necessary on such a standard piece of functionality.

My next step was going to be to step through the procedure line by line, also using SQL Profiler to track down the bottleneck.

Jonathan

May be another suggestion (if you have the possibility to do that).

- Use code coverage to see which tables there are used
- Open the 5.0 beta to see how MS "pre-tuned" these tables in the next version: look at the keys, how they're set up, which properties have which values
- try to do this in your database (after backup of the objects!)

Off course, this is only possible when there is not much changed from 4 to 5 ... and that I don't know.

Good Luck!