{"id":1665,"date":"2009-12-22T13:35:57","date_gmt":"2009-12-22T13:35:57","guid":{"rendered":"https:\/\/www.diaryofanadi.co.uk\/?p=1665"},"modified":"2009-12-22T13:35:57","modified_gmt":"2009-12-22T13:35:57","slug":"importing-a-mysql-dump-to-a-new-database","status":"publish","type":"post","link":"https:\/\/diaryofanadi.co.uk\/?p=1665","title":{"rendered":"Importing A MySQL Dump To A New Database"},"content":{"rendered":"

My web host is 1&1<\/a> – I joined up with them a couple of years ago because they were doing a ‘free year’ offer, and my then web host\u00a0(UKHosts)\u00a0had really annoyed me by being hacked (and whoever did it had deleted all the index files and main images)… but not telling me until some of my clients complained their websites were down, and I<\/strong> called them<\/strong>! (And see the comment right at the end of this article – looks like it may have happened again.) <\/p>\n

The old “we tried to call you when it happened” crap didn’t cut any ice with me.<\/p>\n

Anyway, the great thing about 1&1 is that if you email them with a technical query (or any other type of question come to that), they respond within an hour. UKHosts used to ignore<\/strong> their emails and it was always the same guy who eventually dealt with any query after you’d eventually lost your temper and sent an arsey email. Plus, their phone was permanently engaged or otherwise on answerphone – which they also never used to respond to.<\/p>\n

Anyway, I use WordPress to run this blog. Every so often there is an upgrade to fix bugs or add new features, and so far that hasn’t been an issue. However, with the last upgrade you can only run WordPress from a MySQL database version higher than 4.1.something (I forget which now). Mine was 4.0.something.<\/p>\n

My account allows me to create MySQL 4 and MySQL 5 databases, and in the recesses of my mind I seem to have a recollection that WordPress specifically mentioned MySQL 4 when I first set it up. Therefore, I was running WordPress from the earlier version of a\u00a0MySQL database.<\/p>\n

Creating a new MySQL 5 database was easy – but it was empty! I needed to be able to transfer my old database data into the new one. Everything indicated that this was a walk in the park. An absolute doddle. After all, I had made periodic backups of my database, so I could restore the site quickly if anything ever went wrong. Well, all I can say is, I am bloody happy that I never had to do that. I had plenty of fun and games doing what appears to be a simple operation.<\/p>\n

The only criticism I would have of 1&1 over this was their FAQs. Basically, they are wrong (unless they have updated them as a result of my problem). At best, the FAQs are incredibly misleading – missing out spaces on instructions for command line operations is a guaranteed disaster – and command line systems are not known for being logical in the first place.<\/p>\n

Anyway, without going into huge detail over what went wrong, here is how to do it right (and it was 1&1 who sorted this out for me). I will assume you have created a new MySQL 5 database from within your Admin Panel.<\/p>\n

First of all you need to back up your old database. Go to yourAdmin Panel, go to the MySQL Admin area,\u00a0and choose the database you want to back up:<\/p>\n

\"Select

Select Your Database<\/p><\/div>\n

In the\u00a0PHPMyAdmin area, click on “Export”:<\/p>\n

\n
\"Export

Export The Database<\/p><\/div>\n<\/div>\n

In the database window (shown below), leave everything unchanged except for the tick box (circled) – you want to save your file – and make sure the SQL option is selected:<\/p>\n

\n
\"Select

Select Settings And Save File<\/p><\/div>\n<\/div>\n

Just choose somewhere to save the file where you can find it (call it something simple like ‘dump_db’), then click GO. This will create your backup file.<\/p>\n

Now you need to use your FTP client to upload the ‘dump_db.sql’ file to the root directory of your webspace – that’s the highest level you can go to, above all your folders for your websites.<\/p>\n

All of this was the easy part. 1&1 has various FAQs for importing the dumped database, but none of them worked for me. It turned out my database was too big (it was less than 7MB, but they’d told me it just needed to be less than 9MB for the standard import from MyPHPAdmin to work).<\/p>\n

If you are lucky, clicking on the SQL button will allow you to browse your PC for the dumped file and restore it from there. But I wasn’t<\/strong> lucky. I had to use SSH to complete the restore.<\/p>\n

I downloaded PuTTY<\/a> (an open source\u00a0telnet client). You just run this program from the downloaded file – it doesn’t install anything to your PC. When it opens, it looks like this:<\/p>\n

\"PuTTY<\/a>

PuTTY Settings Window<\/p><\/div>\n

Type in your host name – it’s the name you use in your FTP client and will be something like ‘ftp.yourdomainname.co.uk’. Make sure SSH is selected, then click ‘Open’. You will now get the telnet window, like this:<\/p>\n

\n
\"PuTTY

PuTTY Telnet Window<\/p><\/div>\n<\/div>\n

At the prompt, type in your username (again, the one you use to access your webspace using your FTP client – with 1&1 it’ll be something like ‘u50012345’), then press ENTER. Enter your password (same as your FTP again), and press ENTER. You’ll now see something like this:<\/p>\n

\n
\n
\"Logged

Logged Into Your Server<\/p><\/div>\n<\/div>\n<\/div>\n

Now you’re ready for the most important – and most tricky – part. You’ve got to run a command to copy the dumped database into the new one. It has to be typed EXACTLY right using the EXACT parameters (this was one of the confusing parts of the FAQs, because the usernames and passwords are not what you’d expect unless you’ve done this before).<\/p>\n

Look at your list of databases again (in your MySQL Admin area):<\/p>\n

\n
\"The

The Database List<\/p><\/div>\n<\/div>\n

Those values I have highlighted are the database name, the database username, and the database host name. You’ll also need a password – and this is one which you set up specifically for SSH from your main Admin Panel. Note that the names are for the MySQL 5 database – the one you want to copy your dumped data into.<\/p>\n

At the prompt in the telnet (PuTTY)\u00a0window, you must type the following. It has to be exactly like this (substituting the relevant data from your Admin Panel):<\/p>\n

mysql -h db9876.oneandone.co.uk -u dbo343434343 -p db343434343 < dump_file.sql <\/p>\n

Let me just repeat that, but highlighting the spaces you must type using the symbol “\u2022 ” in red:<\/p>\n

mysql\u2022 -h\u2022 db9876.oneandone.co.uk\u2022 -u\u2022 dbo343434343\u2022 -p\u2022 db343434343\u2022 <\u2022 dump_file.sql<\/p>\n

Press ENTER, then type in your SSH password when prompted, and press ENTER again. The command will execute and your new MySQL 5 database should now contain all your dumped data.<\/p>\n

EDIT 03\/01\/2010:<\/strong> I noticed someone searching for “how to open an sql file and edit”. This is quite simple – you need to use a text editor that doesn’t alter the file by adding headers or messing with file extensions. Notepad++ is an open source program<\/a> and works perfectly for this and other code editing. <\/p>\n

EDIT 22\/1\/2010:<\/strong> In the last two days I have had several hits on the search term “ukhosts hacked”. My experience was well over a year ago (I’ve been with 1&1 for over a year, and I changed to them directly as a result of the example I gave at the start of this article). I can only guess that UKHosts has been hacked again. <\/p>\n

If anyone knows, use the Contact Form from the menu above and give me the details. <\/p>\n","protected":false},"excerpt":{"rendered":"

My web host is 1&1 – I joined up with them a couple of years ago because they were doing a ‘free year’ offer, and my then web host\u00a0(UKHosts)\u00a0had really annoyed me by being hacked (and whoever did it had deleted all the index files and main images)… but not telling me until some of […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[121],"tags":[],"class_list":["post-1665","post","type-post","status-publish","format-standard","hentry","category-latestposts"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/diaryofanadi.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/1665","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/diaryofanadi.co.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/diaryofanadi.co.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/diaryofanadi.co.uk\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/diaryofanadi.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1665"}],"version-history":[{"count":0,"href":"https:\/\/diaryofanadi.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/1665\/revisions"}],"wp:attachment":[{"href":"https:\/\/diaryofanadi.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1665"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/diaryofanadi.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1665"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/diaryofanadi.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1665"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}