Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: TIDB数据导出
|
username: liusu_sky
TiDB Version: 7.5.0
Question: After entering the database and editing the SQL, how can I export the query results to a specified file?
In MySQL, you can check the value of secure_file_priv, which is the default export path, by executing show global variables like ‘%secure%’;. However, executing this SQL in TiDB does not display secure_file_priv.
If the data volume is small, you can directly use SELECT INTO OUTFILE.
If the data volume is large, it’s better to use Dumpling for export.
I tested the export successfully. Is there any way to export it directly as an Excel spreadsheet?
Other available methods such as tee, backup, etc., depend on the export requirements.
I have to recommend the ETL tool Kettle again. In this situation, you probably need to rely on client functions or ETL tools.
Only two steps are needed to complete it. If you want to export and generate an Excel file in the application, it’s better to leave it to the developers to implement.
If the data volume is small, directly use SELECT INTO OUTFILE; if the data volume is large, use Dumpling.
It feels quite useful when the data volume is small.
It’s even better with large amounts of data. Especially with multi-threading support, it can be as fast as you need it to be.
You can specify the export file extension as CSV, and then you can open it with Excel or WPS.
SQL results cannot be directly imported, right? Try using a client like DBeaver.
Kettle tool or have the developers write a dedicated export program.
Set the file extension to CSV format, it should be able to be opened with Excel.
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: