wu-sheng opened a new issue, #10366: URL: https://github.com/apache/skywalking/issues/10366
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar feature requirement. ### Description Currently, with increasing requirements of using SQL database to support medium-scale deployment, from H2 to MySQL/Postgre, then Sharding MySQL. We face the length limitation for tables and indices to limit our flexibility. Here, I want to propose changing the SQL database storage in another way. 1. Merging all tables by referring to the latest ElasticSearch's [`SW_STORAGE_ES_LOGIC_SHARDING=false`](https://skywalking.apache.org/docs/main/next/en/faq/new-elasticsearch-storage-option-explanation-in-9.2.0/) 2. We begin to implement day-based rolling as we had done in ElasticSearch. ### Use case The primary background of this change is due to the super quickly expanding of SkyWalking's monitoring scope. More metrics are being added for various data sources, such as AWS services(#9883) and Airflow(#10341). The database eventually would not be able to support the number of tables. Meanwhile, the scale of monitoring targets could be unbalanced, such as the number of VM is much less than the number of pods and services. ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
