MS SQL Server

In order to achieve top performance, Automic recommends keeping the following notes in mind when installing and operating MS SQL Server.

It is important to reorganize the AE database including all clients regularly because an extensive database affects performance negatively (prolonged access times etc).

Notes

Do not limit resource consumption. Aborting transactions due to limitations specified in the database hamper processing in the AE system. Additionally, inconsistent database contents can occur which cause subsequent errors or endless loops.
Make sure that your server and client has TCP/IP connection enabled (MS SQL Configuration Manager).
The transaction log, the TEMPDB of the database and the page file should not be filed in a RAID 5 file system. Use RAID 1 or 0 instead.
Do not, by any means, activate the option autoshrink in the database. This might occasionally cause a standstill of the Automation EngineDiese Komponente steuert ein Automation Engine-System. Besteht aus verschiedenen Serverprozessen..

Version 2005

Activate "Versioning" to reduce possible deadlocks. Automic recommends storing "tempdb" on a quick device which becomes bigger as a result of using "Versioning"

alter database database name set READ_COMMITTED_SNAPSHOT ON
Add the option Mars_Connection=Yes to the database-connection parameters in the INI files of the Automation Engine and the utilities. This setting ensures optimal database access using the performance options of MS SQL Server 2005.
Example:
SQLDRIVERCONNECT=ODBCVAR=NNNNNNRN,DSN=UC4;UID=uc4;PWD=--1037B2E22BF022EBE2;Mars_Connection=Yes

Version 2008

Activate "Versioning" in order to reduce the occurrence of deadlocks. Doing so has the effect that the file tempdb increases. Ensure that it is stored on a fast device.

alter database database name set READ_COMMITTED_SNAPSHOT ON
Do not use computers with hyper-threading or deactivate hyper-threading.
Split the database to as many files as there are CPUs.