x Want to participate? Join the group to interact
  • State Not Answered
  • +3 person also asked this people also asked this
  • Replies 14 replies
  • Subscribers 138 subscribers
  • Views 21337 views
  • Users 0 members are here
Browse Forums
Announcements
268
topics
260
replies
Databases and Operating Systems
755
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
850
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
876
topics
3k
replies
Sage CRM for Sage 300
182
topics
408
replies
MClark

Erratically slow performance Sage300

Posted By

A customer on a brand new server w/ Server 2012, SQL2012 and Sage 300 is reporting erratically slow response times, though it is getting more pronounced.  They have 5 concurrent users (about 12 workstations), about 5mb in data, no other applications running on the server.  Lots and lots of free space.

Sage 300 is installed on the server - with the volume of data and users they have, I thought this would be OK.  We're doing some mods and I was thinking of managing that process which will continue for some while.

If moving the program files to the workstation will make sense, we can do that, but is that the most effective route to go?  Or are there other things we should look into first?

TIA.

Mary

Parents
  • 0

    Open SQL Server Management Studio

    Open the server Properties

    Open Memory

    Change Maximum server memory to between 50% and 70% of total server memory.

    Click OK - no restart is necessary, this setting applies immediately.

    SQL Server 2012 aggressively uses as much server RAM as possible, leaving no available RAM for other server processes. You can verify this by looking at Task Manager, Performance (Free Physical Memory) and Processes sorted by Memory. You will see SQL server consuming most of the RAM. You want to leave at least 6GB RAM available for the server, so if you have 16GB RAM on the server and set SQL server max memory to 10GB - leaving 6GB for the server. This is documented in a Sage tech note somewhere.

    The other thing is if you are running SQL Server on a VM then you will continue to have issues until you move the SQL server off to a dedicated physical box.

  • 0 in reply to Ettienne Schwagele

    Hi Ettiene, same suggestion applies for SQL Server 2016? We just uprade to Sage 300 2018.1 last week to a new server and users complain about performance but it is a robust new server and very good networking. They have Sage and SQL Server in VM.

Reply Children

*Community Hub is the new name for Sage City