From https://github.com/open-telemetry/semantic-conventions/blob/main/docs/db/database-spans.md#generating-a-summary-of-the-query:
Instrumentations SHOULD capture the values of operations and targets as provided by the application without attempting to do any case normalization.
I'm having second thoughts about this in the context of SQL, where we know operations are case insensitive and it could be odd to see both SELECT table1 and select table1 in metric dashboards.
While you'd still see both SELECT table1 and SELECT TABLE1 in metric dashboards, that's more easily justifiable given that table names are case sensitive in some SQL databases some of the time.