This is confirmed working on a small test set with MySQL 4.1.22
transitioning from SPARC to X64. Thanks everyone!
-Aaron
Here's the test set we used:
CREATE TABLE `test_innodb` (
`id` int(11) unsigned NOT NULL AUTO_INCREMENT,
`bigint` bigint(11) DEFAULT NULL,
`float` float DEFAULT NULL,
Aaron,
"
I've currently got a project to migrate a LARGE (3.5TB) MySQL data set from
a Sun SPARC machine to a Sun x86 machine, both running Solaris 10 (though
obviously one is x86 and the other is SPARC). Is it possible to simply copy
the data files from one host to the other or is a full mysqld
I'm not sure that is true. I haven't seen a case where the
architecture matters. I think the floating-point format is the big
issue; as far as I've seen, even InnoDB stores its data in an
endian-neutral manner.
I am not familiar enough with the SPARC architecture to know whether
it uses IEEE sta
It actually depends on your table types. With MyISAM it is no problem,
but with InnoDB you are looking at a dump-and-restore..
Walter
OlinData: Professional services for MySQL
Support * Consulting * Administration
http://www.olindata.com
On Fri, Feb 13, 2009 at 6:23 PM, Kurt Cypher wrote:
> O
On Feb 13, 2009, at 11:41 AM, Aaron Blew wrote:
All,
I've currently got a project to migrate a LARGE (3.5TB) MySQL data
set from
a Sun SPARC machine to a Sun x86 machine, both running Solaris 10
(though
obviously one is x86 and the other is SPARC). Is it possible to
simply copy
the data f
