SpirirHost Support Centre: MySQL Reference Manual p.105

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

Chapter 2: MySQL Installation 105 The following changes may aect queries in old applications: HAVING must now be specied before any ORDER BY clause. The parameters to LOCATE() have been swapped. There are some new reserved words. The most notable are DATE, TIME, and TIMESTAMP. 2.5.5 Upgrading to Another Architecture If you are using MySQL Version 3.23, you can copy the `.frm', `.MYI', and `.MYD' les between dierent architectures that support the same oating-point format. (MySQL takes care of any byte-swapping issues.) The MySQL ISAM data and index les (`.ISD' and `*.ISM', respectively) are architecture- dependent and in some cases OS-dependent. If you want to move your applications to another machine that has a dierent architecture or OS than your current machine, you should not try to move a database by simply copying the les to the other machine. Use mysqldump instead. By default, mysqldump will create a le full of SQL statements. You can then transfer the le to the other machine and feed it as input to the mysql client. Try mysqldump --help to see what options are available. If you are moving the data to a newer version of MySQL, you should use mysqldump --opt with the newer version to get a fast, compact dump. The easiest (although not the fastest) way to move a database between two machines is to run the following commands on the machine on which the database is located: shell> mysqladmin -h 'other hostname' create db_name shell> mysqldump --opt db_name \ | mysql -h 'other hostname' db_name If you want to copy a database from a remote machine over a slow network, you can use: shell> mysqladmin create db_name shell> mysqldump -h 'other hostname' --opt --compress db_name \ | mysql db_name You can also store the result in a le, then transfer the le to the target machine and load the le into the database there. For example, you can dump a database to a le on the source machine like this: shell> mysqldump --quick db_name | gzip > db_name.contents.gz (The le created in this example is compressed.) Transfer the le containing the database contents to the target machine and run these commands there: shell> mysqladmin create db_name shell> gunzip < db_name.contents.gz | mysql db_name You can also use mysqldump and mysqlimport to accomplish the database transfer. For big tables, this is much faster than simply using mysqldump. In the following commands, DUMPDIR represents the full pathname of the directory you use to store the output from mysqldump. First, create the directory for the output les and dump the database:

MySQL Reference Manual

Home
Hosting Plans \| Domain Registration \| About Us \| Contact Us \| Site Map Terms of Use \| Privacy Policy \| Guarantees Merchant Accounts

SpiritHost - web hosting for spiritual and education sites SpiritHit.com - Religious and Spiritual Portal Copyright © 2002 Dyntex Group, Inc. All Rights Reserved

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide