• State Verified Answer
  • Replies 3 replies
  • Subscribers 15 subscribers
  • Views 688 views
  • Users 0 members are here
Options
Related

SQL Server optimization for GR node

Nenad Kovacevic

Are there any up-to-date documents regarding SQL Server optimization on GR node? The documents I am able to find seem to be outdated and not applicable to the latest versions of SQL Server.

Parents
  • 0

    There was previously a recommendation to run SQL on all CPUs except CPU0. aaGR uses CPU0 and was known to cause lockups or delays on larger systems. I'm not sure this is still a recommendation, maybe someone from Aveva can chime in on this.

    Running a maintenance plan on the GR to reorganize the indexes can also help speed things up.

    Running databases and especially temp databases on fast disks will help.

    If running on a virtual machine, make sure the CPU resources are dedicated and not over provisioned.

    You should also have a look at how many check-ins and deploys you have at any given time. Modern developers tend to check-in and deploy once per line of code they write. I think that would cause locks and wait times.

Reply
  • 0

    There was previously a recommendation to run SQL on all CPUs except CPU0. aaGR uses CPU0 and was known to cause lockups or delays on larger systems. I'm not sure this is still a recommendation, maybe someone from Aveva can chime in on this.

    Running a maintenance plan on the GR to reorganize the indexes can also help speed things up.

    Running databases and especially temp databases on fast disks will help.

    If running on a virtual machine, make sure the CPU resources are dedicated and not over provisioned.

    You should also have a look at how many check-ins and deploys you have at any given time. Modern developers tend to check-in and deploy once per line of code they write. I think that would cause locks and wait times.

Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.