Limit the network protocols supported (TCP/IP). Do not enable other network protocols unless they are needed.
Do not expose a server that is running the M3 BE database to the public internet.
Configure M3 BE instances of SQL Server to use specific port assignments for TCP/IP. Consider to use non-default numbers for the TCP/IP ports.
Consider to separate network traffic between M3 BE application server and the M3 BE database server by using dedicated network interfaces. Ensure that you use the fastest possible connection between M3 BE application server and database server.
Misconfigured antivirus program can cause expensive problems in production, for example, blocking access to critical I/O access and heavy I/O and CPU load, and provide a sense of false security.
If antivirus software is installed, think about that virus protection software requires some system resources to run. You must perform testing before and after you install your antivirus software to determine if there is an impact on performance of the computer running SQL Server.
In addition to the high performing storage requirements, M3 BE database workloads also require proper processing power. The common reason for CPU bottlenecks is insufficient hardware resources.
One of the most important factors that influence SQL Server performance is memory and SQL Server needs a lot of memory. If SQL Server will run short on memory, query response time, CPU usage and disk I/O can increase significantly as Windows begins paging more and more RAM to the hard drive. A good way to keep database server performance is to make sure the database is using as much RAM as possible to avoid to rely as heavily upon disk which is exponentially slower than RAM. The total amount of memory required is directly related to the size of the M3 BE database that is hosted on the server.