top of page

LITIGATION SUPPORT TIP OF THE NIGHT

The views expressed in this blog are those of the owner and do not reflect the views or opinions of the owner’s employer. All content provided on this blog is for informational purposes only. The owner of this blog makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this site. The owner will not be liable for any errors or omissions in this information nor for the availability of this information. The owner will not be liable for any losses, injuries, or damages from the display or use of this information. This policy is subject to change at any time. The owner is not an attorney, and nothing posted on this site should be construed as legal advice. Litigation Support Tip of the Night does not provide confirmation that any e-discovery technique or conduct is compliant with legal, regulatory, contractual or ethical requirements.

See my post on Running Regex Searches With a Grep Utility on the ILTA litigation support blog.

New tips for paralegals and litigation support profesionals are posted to this site each week. Click on the blog headings for better detail.

See How-To Videos on my YouTube channel.

Dealing with large Relativity workspaces on SQL Server

Sean O'Shea
Jun 10, 2020
1 min read

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.

bottom of page