Microsoft Azure Sage Server

We are trying to stand up a server in Azure.  We are using a D4 setup with 16GB of RAM and High Performance SSD.  The performance is a bit worse then our on prem server now.  Does anyone have any experience with this setup?  When I say the performance, I am only testing directly on each server and not thru a workstation. Is there something we are missing, more CPUs, more RAM? 

  • 0

    We have our Sage Server in the Cloud on AZURE. We had to use an RDP (Remote Desktop) Environment to use Sage.  

    Don

  • 0

    We are going to use RD workstations in the cloud as well, my issue is the server isn't performing as well as the on prem server right now and we are trying to scale the server to perform better and I am looking for suggestions.  I am hoping someone has some suggestions as to how the Azure Sage Server was configured.

  • 0

    Is it one of the latest D4 versions? Like a D4s_v5 or D4as_v5? Or, if you need local temp storage, D4ds_v5 or D4as_v5.

    Premium SSD performance varies by size, so if you're I/O limited, you might need to go to a larger SSD even if you don't need the disk space.

    I'd start by running Task Manager and looking at CPU and memory utilization, and Resource Manager to see the disk queue length, and try to identify bottlenecks.

    When you add the remote desktop, you might need to put the server and the remote desktop into a Proximity Group, which will keep the 2 VMs on hosts that are physically close together. Azure regions (East US, for example) can be vast, and contain multiple data centers. Without a proximity group, VM placement is luck of the draw, so latency could be higher than a typical office LAN. I don't know how sensitive Sage 300 CRE is to latency; I am completely new to it. I'm here looking for anyone who's installed it using a server and Azure Virtual Desktop.

  • 0 in reply to Peter Yasuda

    Your input was very helpful.  I was able to track down the issue.  We are running D4 v5 server with Premium SSD.  Your suggestion of watching the resource manager did the trick.  Our GL is not located in the Company Data Folder and is mapped separately in the file locations.  I noticed the network was active and was able to see Sage was looking back to the old server for a lookup of something.  Then it hit me that the file location of the GL folder does not get updated with the Server Migration tool.  Once I updated to the local GL folder everything was faster then the older on prem server.  We will be using Win 10 multi-user workstations located in the same region.