Index Strategy Review for a Busy Table
Choose indexes that help reads without hurting writes.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Review indexes for this table: [TABLE_DEFINITION]. Current indexes: [CURRENT_INDEXES]. Main queries with frequency: [QUERIES]. Write volume: [WRITE_VOLUME]. Database: [DATABASE]. For each query identify the columns used to filter, join and sort, and whether an existing index serves it. Propose new indexes in order of benefit, noting column order reasoning, and list redundant or unused indexes that could be removed. Estimate the storage and write cost qualitatively. Return a table with Query, Current support, Proposed index and Trade-off, a safe rollout using concurrent index creation if supported, and a measurement plan to compare before and after. Ask for the query plans if the information is insufficient rather than guessing. Provide a short method for finding unused indexes by checking usage statistics over at least a full business cycle, including month-end jobs, before removing anything. Describe how to measure the effect of a new index on write latency in a test environment. Add a warning about indexes on columns with very few distinct values and about too many indexes on a table with heavy writes. Include a short record template for each index: purpose, queries served, date added and owner.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.