Upon Export, Old Table/Field Names are Listed in Export

Hi there. I exported my database sql file and the old table and field names were listed in the file. Anything that can be done to fix this problem?

So you created the SQL export file, and then you changed your table and field names?

Please be more precise about the problem.

Sorry! I was sooooo tired yesterday that I was brain dead. ha!

So ... I changed table names and field names in Heidi. Then, I exported the database to an sql file. I opened it up and the OLD table and field names were in that file. I restarted Heidi and tried multiple times, but still the same export with the old names.

Also, after changing the table and field names in Heidi, and trying to save my changes, I had various errors popup warning that the old field name was not present. ha! I had to go login to the server and get the changes actually made.

Thanks for any help you might have! I've always done the structure manipulation via PHPMyAdmin on the server, but just found this software a couple days ago and it's REAL nifty and much quicker. :)

Thanks for your feedback. Glad you nailed it!

To address a related issue, HeidiSQL seems to have trouble remembering file names when exporting data. For example, if I have four databases to back up, with the following paths and names, HeidiSQL will only remember D:\quotation-2026-06-05.sql, not the others. This forces me to re-enter the file names every time I need to back up the data the next day. I believe this problem started about two or three months ago but hasn't been fixed. I'm reporting this to you now, thank you.

Database file names: D:\discuz-2026-06-05.sql D:\manage-2026-06-05.sql D:\maintain-2026-06-05.sql D:\quotation-2026-06-05.sql

No problem here, just tested:

Hi there. Thanks. But, I was referring to the database FIELD names, not the exported FILE name. :)

@designsbycm: Yes, understood. My reply was meant for alan4910's comment.

Oh ok. ha! Thanks!

Hey ansgar ... would you happen to know of a good CRUD generator that has the ability for image/file uploads built into it for textarea fields?

Just doing support for HeidiSQL here. You may insert images with the built-in file processor.

Oh! Ok ... thank you. :)

Hello,

After your previous reply, I tested this again more carefully and found a more specific behavior.

Previously, I only reported that the SQL export filename was not being remembered. At that time, I had not noticed that if I close the SQL export dialog and open it again, the filename is actually remembered correctly.

The problem seems to happen when exporting multiple databases one after another while keeping the same SQL export dialog open.

Steps to reproduce:

1. Open HeidiSQL and connect to a session.
2. Go to Tools → Maintenance → SQL export.
3. Export database test1 to a file, for example: D:\test1.sql
4. Keep the SQL export dialog open.
5. Change the selected database and export test2 to another file, for example: D:\test2.sql
6. Close the SQL export dialog.
7. Open Tools → Maintenance → SQL export again.

Actual result:

Only the last export filename is remembered in the filename history:

D:\test2.sql

The previous export filename is not remembered:

D:\test1.sql

Expected result:

Both export filenames should be remembered in the filename history, because both files were exported successfully during the same SQL export dialog session.

Additional note:

This may explain why your test result looked normal. If I export one file, close the SQL export dialog, and then open it again, the filename is remembered correctly. The issue only appears when multiple exports are performed in the same SQL export dialog without closing it between exports.

@alan4910 yes I can confirm that is a minor bug. Will check if I can fix it at some point.

Thank you for confirming the issue. I really appreciate you taking the time to look into it. 😊

Hello, I have installed the latest release; however, the issue I previously reported is still present. Thank you for your continued assistance.

Hi! Just wanted to follow up and see when you might be able to look into this issue? Having this functionality back would be extremely helpful for users who need to back up multiple databases daily without merging everything into a single file. Thank you for your time and effort!

I wonder wow that could help to merge exports to one file? You were talking about the file history before. And no, I did not yet fix that file history thing.

Note that HeidiSQL provides a zip option in the output drop-down, which may be what you want.

Hi! I think there might be a slight misunderstanding—I do not want to merge exports into a single file.

My use case is that I need to back up multiple different databases into separate .sql files every day.

This is why the file history (remembering previously used filenames/paths) is so crucial for me: it allows me to quickly select the corresponding destination path for each database without having to manually locate or re-type the file path every single time.

I hope this clarifies my intent. Thank you!