Backing up a WordPress database

Hi.

HeidiSQL version: 6.0.0.3889

Would HeidiSQL be a good solution for backing up a Wordpress database that is hosted on my website?

If so I assume I would select "Export database as SQL"?

With the "Table tools" dialog open at the "SQL Export" tab, would it be reasonable to select "One big file" as the output and for the Filename select a location on my local PC?

I don't want to destroy or create anything, just do a backup, so what do I do with the checkboxes Drop/Create against Database(s) & Table(s)?

I have tried doing the above with all items in the left-hand column checked, and leaving the Drop/Create checkboxes on the right-hand side blank.

The database size shown in the left-hand column is 27.8 MB, but the resulting SQL file saved to my PC is only 3KB in size.

Please be explicit with your instructions as I am not an expert at this.

Many thanks.

- Check "DROP" tables
- Check "CREATE" tables
- Leave database checkboxes unchecked
- Select "INSERT" data
- "One big file" and select output filename

Isn't that all intuitive enough? Think I did the right thing when I said I wanted the export dialog not to get more options than it already hase. From time to time there are users asking for additional options and features, while this post seems to state that it should just not get anything more.

Hi Anse.

Thank you -- by following your instructions I appear to have ended up with a valid backup.

Now, perhaps I can do something for you in the form of feedback...

No, I'm afraid that for us MySQL novices, the Export screen isn't "intuitive enough".

The very last thing that anyone wants to risk is damaging or deleting their original database, so it should be quite understandable that we wouldn't want to take any risks if we didn't 100% understand what we were about to instruct HeidiSQL to do.

For example, to us novices the idea of DROPPING a table is cause for some trepidation.

Personally I can't see any problem at all with your providing more Export features if requested by your more experienced users. To me the number of options presented is irrelevant, providing the function of each is simply explained. If there is a note anywhere on exactly what to do to make a backup, I couldn't find it.

HeidiSQL is a fantastic program that allows people like myself, who have no technical knowledge of MySQL, to have more control of our databases than we would otherwise have.

May I suggest that you might want to take into consideration the fact that you are going to have non-expert users, who won't "intuitively" know exactly what to do in every situation where SQL terminology is used.

Again, thanks very much for your prompt assistance.

Ok, then to summarize: "drop" could be renamed to "delete" probably, which is understandable by both novices and experts. Data/"INSERT" + Output/"One big file" should be self-explained, right?

Given that "DROP" is the SQL command used to completely destroy a table, anyone with a minimum SQL background expects the option to have that precise name, and not "DELETE", which is the command to remove rows and keep the table intact. Please don't mess things for expert users.

Totally agree. I think it ends up in teaching newbies to make themself familiar with SQL basics.

As an SQL novice I agree also. There's no reason to "stupidify" accepted terminology, and that's not what I'm suggesting at all.

It's just that if someone is worried about exactly what steps to take to perform a specific task, an easily locatable reference in simple terms would be extremely useful and save having to waste the forums time with elementary questions.

All I needed to allay my concerns were the concise instructions that Anse provided, ie...

To perform a backup do this:
- Check "DROP" tables
- Check "CREATE" tables
- Leave database checkboxes unchecked
- Select "INSERT" data
- "One big file" and select output filename

Job done!