| Author |
 Topic Search  Topic Options
|
agronoy 
Newbie
Joined: 23 February 2006
Status: Offline
Points: 35
|
 Post Options
 Thanks(0)
 Quote  Reply
 Topic: MySQL 8.02 BACKUP
Posted: 14 June 2006 at 2:34pm |
  Hi.
What is the best simple way to backup Mysql database (MySQL client
version: 5.0.19) from the hosting server to my computer using phpMyAdmin 2.8.0.1 on the web.
Please don't save deails...
Thank you
|
 |
agronoy
Newbie
Joined: 23 February 2006
Status: Offline
Points: 35
|
Post Options
Thanks(0)
Quote Reply
Posted: 15 June 2006 at 3:01pm |
|
Maybe I'm wrong and forum database backup is not so important issue....
?
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 15 June 2006 at 3:34pm |
|
I would recommend backing up the database.
However, when it comes to mySQL I tend to stop the service and copy across the mySQL 'data' file from the server. However, in a shared hosting environment this is not an option.
There are tools like SQLyog, which I believe has a mySQL database copy or move tool built into it that could be used to backup a mySQL database.
|
|
|
|
agronoy
Newbie
Joined: 23 February 2006
Status: Offline
Points: 35
|
Post Options
Thanks(0)
Quote Reply
Posted: 15 June 2006 at 4:03pm |
|
Thank you Borg.
I thought I can use the export/import tool on phpMyAdmin but there are so many Check box in the export form that confuse me.
Is it OK to use the export tool? how to configure it?
|
|
agronoy
Newbie
Joined: 23 February 2006
Status: Offline
Points: 35
|
Post Options
Thanks(0)
Quote Reply
Posted: 18 June 2006 at 1:52pm |
Well..... yes thank you...we can use the export tool. About the Check box:
[6.12] I want to understand some Export options.
Structure:
- "Add DROP TABLE" will add a line telling MySQL to
drop the table,
if it already exists during the import. It does NOT drop the table after
your export, it only affects the import file.
- "If Not Exists" will only create the table if it doesn't exist. Otherwise,
you may get an error if the table name exists but has a different structure.
- "Add AUTO_INCREMENT value" ensures that AUTO_INCREMENT value
(if any) will be included in backup.
- "Enclose table and field names with backquotes" ensures that
field and table names formed with special characters are protected.
- "Add into comments" includes column comments, relations, and MIME
types set in the pmadb in the dump as SQL comments (/* xxx */).
Data:
- "Complete inserts" adds the column names on every INSERT command,
for better documentation (but resulting file is bigger).
- "Extended inserts" provides a shorter dump file by using only
once the INSERT verb and the table name.
- "Delayed inserts" are best explained in the
MySQL manual.
- "Ignore inserts" treats errors as a warning instead. Again, more info
is provided in the MySQL
manual, but basically with this selected, invalid values are adjusted and inserted
rather than causing the entire statement to fail.
Nice talking to my self.... 
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 19 June 2006 at 10:13am |
|
The best way to do this is try different methods and see which ones work.
The drop table is good for backups that overwrite existing data, as if an old table exsists it will be deleted and new table made in it's place.
Not sure how the Add AUTO_INCREMENT value thing works in the software you are using, but you need to ensure that the same values are used in the AUTO_INCREMENT ID fields, so try both ways and check the results against the original database to make sure ID fields are the same, this way you will find which one works.
|
|
|
|
