Dealing with large Relativity workspaces on SQL Server

Dealing with large Relativity workspaces on SQL Server

June 11, 2020

Large Relativity databases can either be cached in active memory, or bring up records with high I/O throughput (data transfer speed in megabytes per second) from storage.   A SQL Server table for a Relativity workspace will take up approximately 50 GB of disk space for a million documents.   The SQL Server has RAM limits - the 2016 edition is limited to 128 GB of RAM.  Caching the database in active memory will lead to be better performance.  This is one of the key reasons why an admin may separate productions from a single case into multiple workspaces. 

 

Hardware called Fast Track Data Warehouse can be used to provide the necessary I/O throughput if an entire dataset cannot be cached, but it is expensive and difficult to implement.  It is also possible to store SQL's TempDB system on solid state or flash drives. TempDB is the system database of SQL Server which stores tables and indexes. 

 

 

 

Please reload

Contact Me With Your Litigation Support Questions:

seankevinoshea@hotmail.com

  • Twitter Long Shadow

© 2015 by Sean O'Shea . Proudly created with Wix.com