Specifications and best pratice

Has anyone got a client whose database size is 200GB for sage 300. What should the ideal server specs be if both APP and DB is hosted on one Virtual Machine. Upgraded client from sage 300 2019 to version 2023 for a 31-user sage site by bumping up resources compared to what is given in premium edition table of compatibility guide, but user complains of general slowness in version 2023 during user acceptance testing and wants to sort it out before doing live cutover. 

Is it cause of the new security changes that come with 2023 that could be causing this, or the fact customer has too much historical data - whats the best practices - should we remove data by using clear history and keep to 7 yrs only or there are any other tools out there that helps reduce the DB size from 200GB to something of considerable size. 

Would love to engage specialists who have had experience in this matter - you can contact me on [email protected] and can engage further.

Also between sage 300 2023 and sage 300 2024 - which is more stable ?

Parents
  • 0

    Current 2019 sage that’s  in use in production is on same network (no issues ).

    Just that 2023 is slow - have unticked enable activity logs as well on db setup as well yet no improvements n temporarily disabled anti virus too.  Are there any specific settings related to Sql management studio or ODBc 18 driver  needs a look at ?

Reply
  • 0

    Current 2019 sage that’s  in use in production is on same network (no issues ).

    Just that 2023 is slow - have unticked enable activity logs as well on db setup as well yet no improvements n temporarily disabled anti virus too.  Are there any specific settings related to Sql management studio or ODBc 18 driver  needs a look at ?

Children