sql_cmd_test too easy to fail

super unstable
- fails at high frequency
- too much useless log
- failed test affect subsequent tests, hard to debug real test fails

Look for the sql_cmd_test in the test suite. Examine the test logs to identify the high-frequency failures and the excessive logging. Determine how failed tests affect subsequent ones, possibly due to shared state. Focus on isolating tests and reducing log noise to improve stability.

索引モデルが issue の本文から書いたものです。