Create an Optimization Ticket

An optimization ticket bundles a batch of slow SQL together with optimization settings into a single trackable optimization record: one submission produces a ticket number used to track optimization status, performance gain, and disposition stage on the Slow queries page. It corresponds to the “New query optimization” form opened by the “Optimize” action in Batch Analysis and Optimization.

Goal

Bundle a batch of slow SQL into a single trackable optimization ticket with basic, validation, index, and rule settings.

Prerequisites

One or more slow SQL have been selected on the Slow queries page before opening the New query optimization form.

Start from slow queries

On the Slow queries page, select slow SQL and click “Batch operation → Optimize” (or a single SQL’s “Optimize” button) to open the “New query optimization” page. The page title shows the number of queries involved, e.g. “Create optimization for 1 query”.

Basic configuration

Setting	Meaning
Optimization ID	Unique identifier (ticket number) for this optimization; auto-generated from the time, editable
Index recommendation only	When checked, PawSQL does not rewrite SQL and only recommends indexes on the original SQL

Validation

Setting	Meaning
What-If validation	Connect to the validation database for What-If performance validation (on by default)
Update statistics	Whether to update statistics before What-If validation
Analyze	Whether to actually execute the SQL during `explain`

Index optimization

Setting	Default	Meaning
Deduplicate with existing indexes	on	Whether to deduplicate against existing workspace indexes
Covering index recommendation	on	Whether to recommend covering indexes (avoids table lookups, may use extra disk)
Covering index max columns	`4`	Do not recommend covering indexes beyond this many columns
Index max columns	`4`	Maximum columns in a recommended index
Indexes per table	`5`	Maximum indexes per table; prompt cleanup when exceeded
Max space	`1000`	Maximum space (MB) occupied by all recommended indexes

Rule configuration

Select a rule template (such as “MySQL database audit template”), or enable/disable rules and adjust thresholds inline. Rules are organized into three top-level categories — Object Design, Object Operation, and Data Operation — and can be filtered by severity (notice / warning / critical / disabled). Selecting a template uses its rules and ignores the inline configuration.

Submit

Review the settings and click “Create optimization task”. Optimization runs server-side; results appear in the “Optimization status”, “Last optimization”, and “Performance gain” columns on the Slow queries page.

Expected Result

After submission, the optimization runs server-side and its results appear in the “Optimization status”, “Last optimization”, and “Performance gain” columns on the Slow queries page.

Verification

Confirm the optimization ticket number was created and the ticket is tracked on the Slow queries page.

FAQ

Symptom	Check first
Optimization task hangs	Task queue, concurrency limits, analysis service status
Performance gain shows N/A	Whether optimization ran and completed

​Goal

​Prerequisites

​Start from slow queries

​Basic configuration

​Validation

​Index optimization

​Rule configuration

​Submit

​Expected Result

​Verification

​FAQ

​Related reading

Batch Analysis and Optimization

Track Governance Progress