moving database from local to remote

[tZ]

I am have a toughest time figuring out how to move my database on my local computer to the remote server of my host. I don't know if anyone has had any expierience with godaddy but, I can not figure out how to do this. When I use the import option they have it allows me to download a file but, what file would be my database or where would it be located on the computer? If anyone could help me sort this out it would be most appreciated.

thanks

[panzer]

pc ? or mac
heard some bad press about godady :(

http://error.wordpress.com/2006/01/01/godaddy-sucks/


but every company seems to have there list of go wrongs

but they did have this to say

• Select ‘Web Hosting & Databases’ from the ‘Hosting & Email’ menu at the top of the page.
• Click the ‘Open’ link under the Control panel heading for the hosting account which holds your database.
• Click the button for the type of database you are attempting to manage.
• Click the ‘Open Manager’ button.• Enter your username and password for your database.
• Click on your ‘SQL’ link.
• Click on ‘Browse’.
• Browse to where you have your .sql file located on your machine.
• Once you have found it click on ‘Go’.
• This will upload your database to your hosting account.
Please let us know if we can help you in any other way.

[hewligan]

I haven't used godaddy, but I'd assume it imports from a mysql dump - most places do.

The mysqldump command is explained here:

http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html

[tZ]

I tried this and it returned a syntex error- so what exactly am I doing wrong here?

from what I understand this command will take my database and make it a sql file- right?

mysqldump db_name > backup-file.sql

I replaced the db_name with my databases name as well.

[hewligan]

What was the error?

In a lot of circumstances, I would expect an authentication error on that command. If that's the case, use

mysqldump --user=username --password db_name > dump.sql

[Drazan]

the file should not have any spaces in the name itself. Depending on the upload method it could very well produce a syntax error.

backup file.sql is not valid
backup_file.sql is a valid name.

Also inside the sql file there are some formatting that isn't cross compatible. If you opened it up in a word doc or other editor it may have whitespaces that the uploader doesn't like. Or even the format of the file using ticks or quotes encompasing the fields and info.

If you can post the syntax error, then we can help more specifically.

[JPnyc]

Go daddy's tech-support is pretty good. I would give them a ring

[tZ]

Yeah… I seem to have stumbled upon another promblem and after a day no use can't connect to the appropriate socket. I'm getting this error:


ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)