
CodePudding user response:
First to determine why not go index, what is your statement,Can try to look at the statistics
CodePudding user response:
The SQL and index information and execution plan posted and have a lookCodePudding user response:

CodePudding user response:



CodePudding user response:
The index information is listed on the tableCodePudding user response:

CodePudding user response:
1. The statistics confirm accurate2. Try to hint force index see release the query speed?
CodePudding user response:
Nima 9 indexes, large table query slow suggested that partition