--- title: "Best practices" slug: "best-practices-1" tags: ["Helix Enterprise", "Reference", "Sec Ops and Analytics"] updated: 2026-09-09T16:29:16Z published: 2026-09-09T16:29:16Z canonical: "docs.trellix.com/best-practices-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Best practices The following best practices can help you use TQL effectively. - Use a list and refer to it, instead of using arrays repeatedly. - Do not run regular expressions on a large set of search results. Minimize the search results first and then run regular expressions on them. - Be careful with limit 0. It removes all limitations and causes every event to be returned. - Encapsulate all string patterns with single or double quotation marks to help ensure that Helix Enterprise accurately interprets the string. For example: - `connectionid="1377908085497899" "<search string pattern in rawmsg>" srcipv4:["1.1.1.1","2.2.2.2"]` - `count>"4"` - `eventtime>'2022-04-07T01:10:50:000Z'` - Using spaces and special characters within a `rawmsg` string pattern can result in inconsistent search results. To avoid this, either encapsulate single words with quotation marks as noted above or use the `AND` operator between words. For example: - Use `"incapsula" AND "impreva"` instead of `"incapsula impreva"`. - Use `'username' 'admin'` instead of `'username:admin'`. - Using `:` (contains) instead of `=` (exact match) is recommended for inexperienced users.