Editing SQL Performance

SME is a database oriented application and relies on performance of SQL Server.

For smaller installations, basic server configuration is no problem.  However for companies that have many users and heavy load, it's important that the SQL Server is optimized.  Here are the best practices for SQL server setup in a high volume environment:

# Run full version of SQL Server rather than SQL Express.  Note SQL Express is fine for small installations for example up to 10 to 20 SME users.
# Dedicated Server for SQL:  Move ALL applications off sql server and have sql as a dedicated virtual or physical server.
# Three drives for this dedicated SQL server as follows:
## C drive should only contain the sql server application.
## Drive 2 should be a dedicated drive for the main sql database
## Drive 3 should be a dedicated drive for temp tables and logs.  Recommend that this is a SSD or Hybrid drive for speed.  It does not need to be RAID.
# Increase number of processor cores either as physical or virtual cores.
@@ Line 5: / Line 5: @@
 # Run full version of SQL Server rather than SQL Express.  Note SQL Express is fine for small installations for example up to 10 to 20 SME users.
 # Dedicated Server for SQL:  Move ALL applications off sql server and have sql as a dedicated virtual or physical server.
-## In an ideal environment the SQL server should not be used for any applications other than SQL.  We have many companies running SQL/SME/and QB from the SQL server without performance impacts. No other applications should be installed on the SQL server with the exception of the above and necessary maintenance utilities.
 # Three drives for this dedicated SQL server as follows:
 ## C drive should only contain the sql server application.
 ## Drive 2 should be a dedicated drive for the main sql database
 ## Drive 3 should be a dedicated drive for temp tables and logs.  Recommend that this is a SSD or Hybrid drive for speed.  It does not need to be RAID.
-### Separate drive for the Temp databases and Logs – in our experience systems running a SSD, or hybrid SSD/traditional combined drive, for the temp database and logs experience better performance since they are the SQL components with the highest read/write drive demands. They do not need to be part of the raid. Some companies choose to keep the temp databases and logs on the raid but set them up in a separate partition.
 # Increase number of processor cores either as physical or virtual cores.
-# All clients must be using the latest SQL Native Client for the version of SQL you are running. In your case use the latest 2008 native client. This is especially true for any machine still running the XP operating system. You can download that from here:
-##   Use for all 64 bit machines: http://high5software.com/downloads/SQL/SQL2008/sqlncli_x6408.msi
-##   Use for all 32 bit machines: http://high5software.com/downloads/SQL/SQL2008/sqlncli_x8608.msi
-##   Open the firewall ports on clients to the server port TCP 1433 and UDP 1434
-##   Set exceptions in all A/V software for the sme5.exe on the server and, depending on the A/V software, add the ports noted above
-##   Do not install the 2012 Native Client as that will cause issues on the XP machines
-# Network: We strongly suggest you run an analysis tool, such as Wireshark, on your network and benchmark connectivity between the SQL server and all clients to assure there are no issues.  We’ve had many calls regarding degraded performance that resolved out to either faulty network cards, bad cabling, and failing switches.  We also suggest you do not use wireless connections since in our experience they have a significant impact on performance.