---
schema_version: "1"
id: fe6c324e8ab6b65b7b5ee8a5495c82065f81985e83682633c301e984911344a0
title: Searching
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform/salesforce-large-data-volumes-bp/guides/cce/ldv-deployments/ldv-deployments-best-practices-searching.md
canonical_url: https://developer.salesforce.com/docs/platform/salesforce-large-data-volumes-bp/guide/ldv-deployments-best-practices-searching.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 9ef912c65f2b9b7af4d0a9b0ef905373fea155416f6637a91166da35b5b0ad99
products:
  - Best Practices for Deployments with Large Data Volumes
  - Platform Developer Content
---

# Searching

|Goal|Best Practice|
|----|-------------|
|Reducing the number of records to return|Keep searches specific and avoid using wildcards, if possible. For example, search with `Michael` instead of `Mi*`.|
|Reducing the number of joins|Use single-object searches for greater speed and accuracy.|
|Improving efficiency|Use the setup area for searching to enable language optimizations, and turn on enhanced lookups and auto-complete for better performance on lookup fields.|
|Improving search performance|In some cases, partition data with divisions. (See [Divisions](https://developer.salesforce.com/docs/platform/salesforce-large-data-volumes-bp/guide/ldv-deployments-infrastructure-divisions.md).)|
|Reducing the time it takes to index inserts and updates for large data volumes|See [Search Architecture](https://developer.salesforce.com/docs/platform/salesforce-large-data-volumes-bp/guide/ldv-deployments-concepts-search-architecture.md).|