If you deploy MOVEit Transfer to use MS SQL Server, it is best practice to run TempDB on high-performance storage. For example, since Version 8.2, MOVEit Transfer uses Read Committed Snapshot Isolation (RCSI) to mitigate latency and concurrency issues you might realize in large installations (millions of files).

RCSI for MS SQL Server introduces a dependency in order to relieve concurrency problems. Using this feature, TempDB can be leveraged heavily during read and write transactions. It is important for large scale implementations to use high performance storage for TempDB (for example, local RAID 1 or RAID 1+0 can provide advantages). Consult your database administrator for tuning large installations.

Note: Errors or exceptions observed in TempDB should be closely examined. RCSI expects the availability of TempDB.

Sizing/Volume Placement

Follow these guidelines when planning out SQL Server database sizing:

  • Log growth drives database size (and SQL Server defaults to auto grow).
  • Logs and tempdb files should be placed on distinct write-optimized volumes.
  • Where MOVEit Transfer Server typically has many more read transactions than writes, the primary data file can be read-optimized.