[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-09(UTC)"],[],[],null,["# Search versus secondary indexes\n\n| **Note:** This feature is available with the Spanner Enterprise edition and Enterprise Plus edition. For more information, see the [Spanner editions overview](/spanner/docs/editions-overview).\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThis page describes the features for search and secondary indexes.\n\nWhen deciding between search indexes and secondary indexes, keep in mind that\nsearch indexes should be the default choice for full-text use cases and\nsecondary indexes should be the default option for everything else. The\nfollowing table describes when to use each type of index.\n\nBesides semantics, the syntax of the DDL statement to create a search index is\ndifferent from the DDL syntax to create a secondary index:\n\n- Indexed columns are defined separately from the sort order in the search index.\n- The order of `TOKENLIST` columns in the `ON` clause of the `CREATE\n SEARCH INDEX` statement is immaterial.\n\nWhat's next\n-----------\n\n- Learn about [search indexes](/spanner/docs/full-text-search/search-indexes).\n- Learn about [secondary indexes](/spanner/docs/secondary-indexes)."]]