x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 2 replies
  • Subscribers 43 subscribers
  • Views 2308 views
  • Users 0 members are here
Browse Forums
Announcements
68
topics
93
replies
Customization and Integration
262
topics
822
replies
Financials, Projects, and Administration
382
topics
843
replies
General Discussion
327
topics
836
replies
Installation and Technical Issues
335
topics
1k
replies
Manufacturing, Distribution, and Applications
341
topics
696
replies
Reporting and Analytics
123
topics
480
replies
DanBarryAFLCIO

Slow performance on MAS 500 ERP after switching to an offsite data center

Posted By

We have experienced slow performance and drops in the connection to our SQL Server since we switched our Windows 2008 R2 (with SQL Server 2008 R2) to an offsite data center. Prior to this everything was located in-house (same building, same floor). Has anyone else experienced something similar after switching to a data center and have they found any resolutions?

We have increased our timeouts on the client machines and this has seemed to resolve the disconnects to our MAS 500 SQL Server DB, but performance still suffers and everything runs more slowly. See attached file for timeout error in obj manager (objmgr)

Thanks in advance,

Dan Barry

  • 0

    Dan I would imagine there are lots of ugly constraints on an offsite SQL server for MAS 500.  Especially if you do heavy view use and/or reporting.  You made no mention of your internet connection.  I guess one of the first things I would do is go into the Invoice view and pull a large range of invoices up.  Time it.  Then go to sql server and do the same query in query analyzer/sql management studio.  If management studio is slow then you know it's your connection.  Hopefully that helps a little.  I assume that your clients are local?

    John

  • 0

    If you are running the Sage 500 ERP client from the local desktops attempting to connect to Sage 500 ERP SQL Server DB over the wire this is not technically a supported configuration. You will most likely need to have a Windows Terminal Server 2008 (or Citrix) created at the offsite data center, install your clients their and publish the app for your clients to connect.

*Community Hub is the new name for Sage City