Hi, ----- Original Message ----- From: "Richard S. Huntrods" <[EMAIL PROTECTED]>
> Basically, the "mysqldump" output is missing the "use xxx" command to > change to the target database. I have a perl script that does that (and > extracts the table defs to another file for documentation). Have a look at the options you can use for mysqldump (mysqldump --help)... --databases allows you to specify specific databases, and the output will then contain USE commands too. (--all-databases is a shortcut for --databases with all dbs specified.) You can use --no-data to get a dump with ONLY the table defs. Easy! ;-) Also see the mysqldump section in the manual (http://www.mysql.com/doc/m/y/mysqldump.html). > I have database mysqldump outputs that were 15 megabytes [...] > I have never had any problem. Now, perhaps 10-15 megs is not considered > "large". Well, we started in August with a 2 meg database, and we're > adding users every day. We currently have 775 users, but may expand to > over 10000 before this time next year. What lots of people regard as 'large' or 'huge' is actually pretty small, considering there are terabyte size production installations of MySQL servers ;-) Importing a dump file is simply executing a list of CREATE DATABASE/TABLE followed by INSERT statements. It's nothing special. If if causes problems, there are a meriad of possibilities including source bad compiles and operating system problems. I'm sure anyone would agree that a quick&sloppy installation from source by a disinterested ISP who is not knowledgable about MySQL, is a sure recipe for disaster.... However, the article provides no info on it so it's really impossible no tell. We don't have operating system info, MySQL version info, compile info (if installed from source), configuratation, or anything else. Most unfortunate. > I'll keep this list posted of any problems, but so far the performance > has been exceptional. Indeed, posting a problem on the list, together with all relevant info as described above, is very useful. Often the issue is resolved quickly with info from another user. And occasionally, a bug IS found, which can then be fixed by the developers. > However, once I had downloaded and installed MySQL, I became a convert. > MySQL is very robust, VERY fast, and has a very tiny footprint compared > to other database products. Thanks! ;-) Regards, Arjen. -- MySQL Training Worldwide, http://www.mysql.com/training/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Mr. Arjen G. Lentz <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Technical Writer, Trainer /_/ /_/\_, /___/\___\_\___/ Brisbane, QLD Australia <___/ www.mysql.com --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
