Sage 200 Manufacturing performance

SUGGESTED

Now I know that Sage doesn't support the manufacturing part of Sage 200 anymore (Sicon didn't work for us) but we have an issue that mostly seems isolated to works orders that seems to be related to the opening and/or editing of WO's whereas the screen is VERY slow to load. I had seen something somewhere about the WO SQL tables being VERY badly indexed, but I need to know if there is a way to improve this?

Any help would be cool as it takes our Production department a lot longer to do stuff than it should be. This is not server performance or anything like that as every other part of Sage works fine, we have been using the sales and accounts parts of Sage for years. 

Cheers.

  • 0

    Hi Derek, 

    We do still support the Sage 200 Manufacturing module, though its in extended support.

    This means that as long as your Sage 200 version is supported under our lifecycle policy we'll provide 2nd line support to your Sage Business Partner, where they need it. A definition of what we cover in extended support is also outlined in the policy.

    Feel free to send me an email [email protected]

    kind regards

    Jo

  • 0

    This is a topic that I don't have time to go into a huge amount of detail about right now, but I've done a lot of work for several of my Sage 200 clients to improve things in this area.

    It's not really possible to make the claim that the tables are *badly* indexed. Certainly your indexes should be rebuilt regularly to ensure fragmentation is kept to a minimum (although TBH index fragmentation is far less of a problem than people seem to think) and to ensure the statistics are up to date (more important IMO). Outside of that it's really necesssary to monitor some of SQL Server's DMVs (sys.dm_missing_index_details for one) as what you're looking for is query plans which report that they'd perform better if a particular index was present. This is data that you need to gather over a meaningful period of time (like a typical working week).

    Beyond index optimisation (and, of course, making sure that SQL Server is in good nick overall), I have resorted to refactoring some of the Stored Procedures that manufacturing uses (there are some amazingly inefficient ones!) and also written some 'lightweight' forms - for example one client is constantly needing to manipulate the start/end/due dates on their WOs as part of how they manage their production schedule. I wrote a form to let them do just that, and as it loads up far less data than the standard 'Amend Works Order' form it's considerably more performant. Maybe that's something your Sage Business Partner could consider if it would help in your case (I don't know your use case around editing WOs).

  • 0
    SUGGESTED

    Hi Derek,

    If you haven't already, please contact your Sage Business Partner as suggested below who should be able to help. If they do require assistance or guidance from us, they can then get in touch to directly discuss this issue.

    Kind regards,