Posted on: March 12, 2015in Blog
5 Helpful Tips on Running Basic Searches in Relativity
Have you ever had problems with long-running queries in Relativity? Here are some best practices to help make your searches run faster.
1. If your search only includes a specific range of documents, or documents in a specific tag, always make sure you enter those conditions first.
This will allow the system to cull down to the specified group before running any keywords or metadata conditions. I have also found that by adding all of the “OR” conditions before adding the “AND” conditions, seems to reduce the amount of time it takes to return my results.
2. Use a HASHJOIN query hint if you are running searches on a very large dataset (1 million documents or higher) and the condition to include family.
Enter the hint HASHJOIN:TRUE in the Query Hint box. Do not use this query hint on all searches including family as it can have adverse effects as described below.
As the hash table size grows, it requires more CPU and memory, so this function should only be utilized in a subset of queries where you are including family. Hash joins deliver the most performance improvement for large datasets when two or more tables are joined together, and one or more of them have no index or are not sorted.
3. Use the lists feature within Relativity when you want to reference another search that has more than one condition.
You do not want to do this on a search that will change as documents are coded or new data is loaded, unless you are certain the list has been updated to the most recent set of documents. However, if you are using a search that is pulling in static information (such as a list of productions) this could be very helpful. It is much faster to add a list condition as opposed to setting the conditions for pulling in all or specific productions.
Below is an example of adding three static conditions that could easily be turned into a list.
Make sure your list names are very specific for easy identification. Also, if you are using lists and updating them intermittently, tack on the date to the end of the name.
4. For quality control, always consider adding the fields contained in the conditions to your view.
We all make mistakes and this is a good way to QC your search. If it is not considered an invalid search query, you will get results. When you accidentally join them with an “OR” condition rather than an “AND” condition, you could be looking at irrelevant data. When you add the fields to your view, you are more likely to notice issues, such as information that you intended to exclude appearing in the search results.
5. Use trial-and-error to quality control check searches that contain multiple choice/object fields.
Always QC your results, especially if you are getting specific choices back that you attempted to exclude. Try changing the operator in the conditions from “These conditions” to “Not these conditions”, and then do the same on the popup window and select the opposite to what you had previously. This will fix your result set. If it doesn’t, confirm that you are not pulling in family on the search – this would also cause false/positives to appear in the results.
Below are examples of when you may be in the situation that merits a change in the operator.
From your search conditions view:
Once you click on the browse button from the above condition:
Keeping these best practices in mind while using the saved searches feature in Relativity will help you attain high-quality search results at a faster pace.
D4 Weekly eDiscovery Outlook
Power your eDiscovery intellect with our weekly newsletter.
Posted November 16, 2017
5 Workflow Tips for Conducting a Foreign Language Review
Posted November 10, 2017
What You Need to Know About Managed Review and the eDiscovery Process
Posted November 02, 2017
7 Steps to Help You Defensibly Migrate eDiscovery Data
Posted October 27, 2017
CLE Webinar with Lewis Brisbois: How to Do Social Media Collection and Presentation Right
Posted October 26, 2017
Despite Clawback, Defendant’s Reckless Abandon of Rule 502 Bites Back
Posted October 20, 2017
How to Use the eDiscovery PST Export Tool in Office 365 E3
Posted October 12, 2017
Recent eDiscovery Cases for Mobile Phones and Social Media
Posted October 05, 2017
Raising Objections to the Format of ESI Productions: Do it Early and Do it Clearly
Posted September 27, 2017
5 Reasons eDiscovery Alternative Fee Models Make Sense for You
Posted September 22, 2017
Why it's Crucial to Have a Corporate Mobile Device Policy