Restore Database Problem

Wow, that was a fast answer, thanks! 🙂

Unfortunately, I dont get it yet: I have BBEdit and a backup of my sql-file; but what is it precisely that has to be edited?
Here’s a bit of the sql-file, it’s the part with the categories: do you want me to delete everything between “CREATE TABLE” and “… AUTO_INCREMENT=6 ;”?
Of course, there are a lot of instances of text-blocks like this.

——————from the .sql-file—————————–

— Table structure for table wp_categories
—

DROP TABLE IF EXISTS wp_categories;
CREATE TABLE wp_categories (
cat_ID bigint(20) NOT NULL auto_increment,
cat_name varchar(55) NOT NULL default ”,
category_nicename varchar(200) NOT NULL default ”,
category_description longtext NOT NULL,
category_parent int(4) NOT NULL default ‘0’,
PRIMARY KEY (cat_ID),
UNIQUE KEY cat_name (cat_name),
KEY category_nicename (category_nicename)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=6 ;

—
— Dumping data for table wp_categories
—

INSERT INTO wp_categories VALUES (1, ‘General’, ‘general’, ”, 0);
INSERT INTO wp_categories VALUES (2, ‘Generisch’, ‘generisch’, ”, 0);
INSERT INTO wp_categories VALUES (3, ‘Bla√É≈âˆ?rot’, ‘bla%c3%9frot’, ”, 0);
INSERT INTO wp_categories VALUES (4, ‘Veilchenrot’, ‘veilchenrot’, ”, 0);
INSERT INTO wp_categories VALUES (5, ‘Schwarzrot’, ‘schwarzrot’, ”, 0);

———————————————————-

Actually, I was thinking that I could fix something about the charset-encoding when exporting the database, in order to get a sql-backup-file which is suitable for the MySQL on the server-site. Wrong idea?
I mean, I thought I could adjust the exported db-information in any way necessary.

Would be great if you could give me another hint. Sorry, being new to all this stuff.

Well, thanks to your advice, it worked — somewhat, that is.
The server’s MySQL took my sql-backup-file, but: it screwed the german Umlaute (like: ä ö ü, etc.) throughout the WP-installation.

And, what is worse, but probably a different problem: all links internal to WordPress still direct towards my local site, i.e.: they all start with “http://127.0.0.1” instead of “http://auteuil.au.ohost.de”.
Even http://auteuil.au.ohost.de/wordpress/wp-login.php changes immediately/gets ‘forwarded’ to http://127.0.0.1/wordpress/wp-login.php.

Any further advice? would be great—

Thanks for your further reply — unfortunately, although I followed the instructions regarding correcting the siteurl, and although I double-checked that the url was indeed appropriately changed, the wp-internal-links still direct wrongly to my local machine.
Neither any progress on the german Umlaute-site of things. I double-, triple-checked all the charset-encodings of the engaged databases and WP’s — to no avail. All utf-8.

I think I try a fresh install, since I never had such issues before.

I am still very interested in figuring out how to swap databases between local machine and server-installation. So if anyone could give a helping hand, this would be very much appreciated. Thanks to podz for helping me out so far.

Oh goodness, you’re right: I missed to change the home value, I didn’t realize that there is more than one page in ‘Browse’. Although your page was perfectly clear about that, that was my fault.
I have to say though, that in the by now fresh installation there is no value given for ‘home’, although there is a value for siteurl.

Ok, anyway, I re-installed my WP and now the WP-internal-links link in a good way and the german Umlaute are treated well again so far.

Now, I haven’t yet tried again to upload my database-file, being really afraid that things get messed up again due to some charset-encoding-issues which I still do not understand.

Well, I think I am too curious to not give it another try … 🙂

podz: the remaining issue are the screwed german Umlaute!

Even without understanding german too well, I guess, you could see the strange ‘string-patterns’ at: http://auteuil.au.ohost.de/wordpress/

Thanks for being around all day! such a bless …

Well, it seems (german WP-forum) there are some unresolved issues regarding charset-encoding — fortunately, newly edited posts show up fine on my blog; since I just get started I am going to hand-edit the rest.
Still, compatibility between different MySQL-/, charset-encoding-versions (or whatever) is still on my wish-list.