Required hardware configuration for SQL and AVEVA Mobile Operator server

Based on the application size, you can use the following table to understand the required hardware configuration for SQL and AVEVA Mobile Operator server.

Note: These are the recommendations in a scenario where only there only AVEVA Mobile Operator database and AVEVA Mobile Operator services are running in the server. However, if you have other product databases running, then you must refer to the recommendations provided for that product.

SQL Server Settings Recommended on a Typical Workload:

SQL Server Settings on a Typical Workload is recommended by Microsoft based on our internal stress testing. Depending up on your actual workload (that is, multiple databases in the same SQL server and have variable workloads), contact Microsoft team to understand the required settings.

• High speed drives for the data (SAN) with separate storage for SQL log, data, and temp files.

• Set power plan always to High.

• Set MAXDOP to 1.

• Enable “lock pages in memory”. Assign lock pages to SQL Service account.

• RAM settings: Following are some of the examples for the RAM settings:

  • If your SQL box has 64 GB, then assign 56 GB to SQL Server and the rest to the Operating System.

  • If your SQL box has 16GB, then assign 12 GB for SQL and the rest to Operating System.

  • If your SQL box has 32GB, then assign 28 GB for SQL and the rest to Operating System.

  • If your SQL box has 128 GB, then assign 120GB for SQL and the rest to Operating System.

    These assumptions are based on:

  • Machine is a pure database server without any application.

  • If you have multiple SQL server installation, you have divided the memory based on the load.

• Have TempDb and actual DB in separate disk files.

• Split the TempDb to multiple files (based on the size of the TempDb):

  As a rule, if the number of logical processors is less than or equal to eight (8), then use the same number of data files as logical processors. If the number of logical processors is greater than or equal to eight (8), then use eight data files. For example, if you have allocated 16 GB for the TempDb and have 8 logical processor, split the database into 8 files each with 2 GB.

• Perform routine maintenance with index rebuild or reorganization.

• If reports like SSRS and Auditor Plus that has large data set or take more time for retrieval, it is always good practice to execute them on the read replicas of the main database. By doing so, it will not impact the main database and application performance when the sync and other mainstream use cases are happening on the main database.