Hey,
happy new year and I do have a question what might be the best way to
migrate some different databases to a new central server.
The question came up as I wanted to put our web CMS database on our
newer master/slave mysql installation.
We run red hat el 4 and 5 right now, so the source db is
On Thu, Dec 9, 2010 at 9:10 AM, Shawn Green (MySQL)
wrote:
> On 12/8/2010 22:50, Robert Citek wrote:
>>
>> Greetings to all,
>>
>> Can I migrate slave databases between slave servers?
>>
>> Imagine the following scenario: I have one master database server with
>> 10 databases. I also have two sla
On 12/8/2010 22:50, Robert Citek wrote:
Greetings to all,
Can I migrate slave databases between slave servers?
Imagine the following scenario: I have one master database server with
10 databases. I also have two slave database servers, one replicating
5 of the 10 databases, the other replicati
Greetings to all,
Can I migrate slave databases between slave servers?
Imagine the following scenario: I have one master database server with
10 databases. I also have two slave database servers, one replicating
5 of the 10 databases, the other replicating the other 5 databases.
Can I migrate on
> 2. Don't stare at the screen. Start it, script the process & have it email
> your phone when it's done. Do something else in the mean time.
I don't literally stare at the screen -- of course I script it and do
other things.. but when I have a resource limited environment, it sure
would be ni
In the last episode (Sep 28), Gavin Towey said:
> Also note, 5.5 isn't production ready. 5.1 is the current GA release.
5.5 is really really close, though (5.5.6 is marked as Release Candidate),
Better to switch now while you're already doing a migration, and then
install 5.5.x updates as they ha
Also note, 5.5 isn't production ready. 5.1 is the current GA release.
-Original Message-
From: Hank [mailto:hes...@gmail.com]
Sent: Tuesday, September 28, 2010 3:29 PM
To: mysql@lists.mysql.com
Subject: Migrating my mindset from MyISAM to InnoDB
Primarily due to many positive
Hank [mailto:hes...@gmail.com]
Sent: Tuesday, September 28, 2010 3:29 PM
To: mysql@lists.mysql.com
Subject: Migrating my mindset from MyISAM to InnoDB
Primarily due to many positive posts I've seen about MySQL 5.5 and
advances in InnoDB, I'm seriously considering converting all my MyISAM
data
Primarily due to many positive posts I've seen about MySQL 5.5 and
advances in InnoDB, I'm seriously considering converting all my MyISAM
databases to InnoDB. I don't need many of the InnoDB features, but
if I'm going to upgrade from 4.1.14 to 5.5, I might as well bit the
bullet since that seems
> Oracle will sell it if they can convince the customer.
Any one who has had the pleasure of using Oracle Application Server
can attest to that.
--
- michael dykman
- mdyk...@gmail.com
May the Source be with you.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
database. I would also bet that 80% of the people who are actually
writing queries with that many joins don't have a solid grasp of the
fundamental principles of relational database design.
Why not? Normalizing gets you -more- tables, not less.
And normalizing is a goal in itself? I've seen
Martijn Tonies wrote:
Martijn Tonies wrote:
database. I would also bet that 80% of the people who are actually
writing queries with that many joins don't have a solid grasp of the
fundamental principles of relational database design.
Why not? Normalizing gets you -more- tables, not less.
A
Tom,
I noticed the article didn't say how much money you'll save by not paying
through the nose for Oracle per server licensing, the cost of upgrading
your hardware to get some speed out of Oracle, or the cost of having to
hire one or more Oracle administrators to manage and tweak the database.
Martijn Tonies wrote:
database. I would also bet that 80% of the people who are actually
writing queries with that many joins don't have a solid grasp of the
fundamental principles of relational database design.
Why not? Normalizing gets you -more- tables, not less.
And normalizing is a g
joins?
Oracle will sell it if they can convince the customer.
Just some thoughts.
- Original Message -
From: "Tom Worster"
To: "mos" ;
Sent: Sunday, January 31, 2010 7:39 PM
Subject: Re: 50 things to know before migrating from Oracle to MySQL
On 1/29/10 5:0
On 1/29/10 5:03 PM, "mos" wrote:
> I noticed the article didn't say how much money you'll save by not paying
> through the nose for Oracle per server licensing, the cost of upgrading
> your hardware to get some speed out of Oracle, or the cost of having to
> hire one or more Oracle administrators
On 01/29/2010 07:24 PM, Shawn Green wrote:
> Rudy Lippan wrote:
>> On 01/29/2010 02:57 PM, Chris W wrote:
>>
>>> Hardcore stupid if you ask me. I suppose it is "possible" to have a
>>> valid reason (can't imagine what it might be) for using more than 61
>>
>> How about complex data requirements?
Rudy Lippan wrote:
How about complex data requirements? Depending on the resolution of
your data set, I could see a "simple" person-type object that contained
name, address, SSN, mother, and birth_info starting to approach the limit.
Cities change, address changes, names change, and even mother
Martijn Tonies wrote:
database. I would also bet that 80% of the people who are actually
writing queries with that many joins don't have a solid grasp of the
fundamental principles of relational database design.
Why not? Normalizing gets you -more- tables, not less.
And normalizing is a goa
Rudy Lippan wrote:
On 01/29/2010 02:57 PM, Chris W wrote:
Hardcore stupid if you ask me. I suppose it is "possible" to have a
valid reason (can't imagine what it might be) for using more than 61
How about complex data requirements? Depending on the resolution of
your data set, I could see a
On 01/29/2010 02:57 PM, Chris W wrote:
> Hardcore stupid if you ask me. I suppose it is "possible" to have a
> valid reason (can't imagine what it might be) for using more than 61
How about complex data requirements? Depending on the resolution of
your data set, I could see a "simple" person-ty
... or 50 ways to leave your Oracle...
... or 50 ways to save your money...
Choose mysql! :)
--
Jørn Dahl-Stamnes
homepage: http://www.dahl-stamnes.net/dahls/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arc
as a relatively unsophisticated dbms user (just dynamic web site back
end),
i thought it was very interesting to see the kinds of things oracle users
do
that i'd never have imagined.
more than 61 joins in a query?! man, those guys are hardcore.
Hardcore stupid if you ask me. I suppose it i
At 01:57 PM 1/29/2010, Chris W wrote:
fsb wrote:
as a relatively unsophisticated dbms user (just dynamic web site back end),
i thought it was very interesting to see the kinds of things oracle users do
that i'd never have imagined.
more than 61 joins in a query?! man, those guys are hardcore.
fsb wrote:
as a relatively unsophisticated dbms user (just dynamic web site back end),
i thought it was very interesting to see the kinds of things oracle users do
that i'd never have imagined.
more than 61 joins in a query?! man, those guys are hardcore.
Hardcore stupid if you ask me. I
25. Each table can have a different storage backend (”storage engine”).
Yes, we absolutely allow this.
Each engine brings a certain strength to the storage and retrieval
solutions you can create with MySQL. We explicitly recognize that there is
no "one size fits all" approach that meets the ne
Hmmm... I find it suspicious that there are *exactly* 50 things you need to
know before migrating from oracle to mysql. Not 49. Not 51. Exactly 50.
Well, he did repeat that clustering is not what you think it is so I guess
it technically is 49. But I wonder what would happen if he thunk up a
On 1/28/10 5:21 AM, "changuno" wrote:
> Hi folks,
>
> Read a blog which states 50 things to know before migrating from Oracle to
> MySQL. Any comments on this?
as a relatively unsophisticated dbms user (just dynamic web site back end),
i thought it was very interesti
Doesn't Google run MySQL ?
Hmmm
On Thu, Jan 28, 2010 at 4:56 PM, Carl wrote:
> A quick Google turned up
>
>
> http://www.xaprb.com/blog/2009/03/13/50-things-to-know-before-migrating-oracle-to-mysql/
>
> Man, I love Google.
>
> Thanks,
>
> Carl
>
A quick Google turned up
http://www.xaprb.com/blog/2009/03/13/50-things-to-know-before-migrating-oracle-to-mysql/
Man, I love Google.
Thanks,
Carl
- Original Message -
From: "Daevid Vincent"
To:
Cc: "'changuno '"
Sent: Thursday, January 28, 2010 5:4
> -Original Message-
> From: John Meyer [mailto:johnme...@pueblocomputing.com]
> Sent: Thursday, January 28, 2010 2:16 PM
> To: mysql@lists.mysql.com
>
> On 1/28/2010 3:21 AM, changuno wrote:
> > Read a blog which states 50 things to know before migrating
>
On 1/28/2010 3:21 AM, changuno wrote:
Hi folks,
Read a blog which states 50 things to know before migrating from Oracle to
MySQL. Any comments on this?
would it have been too much to just link to it?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To
Shawn Green wrote:
> 23. There are fewer and less sophisticated tools for administration.
>
> MySQL doesn't need them. That alone should tell you something about
> our reliability.
>
This speaks to simplicity-- both in terms of easy to use and in terms of
more limited features. It says nothing
changuno wrote:
Hi folks,
Read a blog which states 50 things to know before migrating from Oracle to
MySQL. Any comments on this?
... list snipped ...
MySQL was never designed to be a clone of Oracle (the database). We
have distinct differences in design and implementation that make us a
anguno wrote:
> Hi folks,
>
> Read a blog which states 50 things to know before migrating from Oracle to
> MySQL. Any comments on this?
>
> 1. Subqueries are poorly optimized.
> 2. Complex queries are a weak point.
> 3. The query executioner (aka query optimize
Hi folks,
Read a blog which states 50 things to know before migrating from Oracle to
MySQL. Any comments on this?
1. Subqueries are poorly optimized.
2. Complex queries are a weak point.
3. The query executioner (aka query optimizer / planner) is less
sophisticated.
4. Performance
Hi,
I plan to migrate a 32 bit MySQL installation to a 64bit host.
(mysql-5.0.77)
Both servers are RedHat EL 5.4 with the original mysql rpm.
The "simpel" plan was to shut down mysql and than copy the db-files from
/var/lib/mysql/ from host to host.
Any suggestions? Or comments? Or should I exp
Hi!
Trying to migrate from Netware to Suse (SLES 10 sp 1 NOWS SBE 2).
I already changed the my.cnf file:
1.added a datadir=/MySQL/data line
2.removed the comments from all INNOdb lines
The tables on the Netware files are not big
On the SLES server I already see a mysql folder containing tables
Shaun Adams schrieb:
> When I perform a dump in mysql5 to mysql 4 DB, I get the error (below).
> Does anyone know how I can resolve this?
>
>
>
> QUERY (windows server from the cmd prompt)
>
> mysqldump --lock-tables --user=root [SOURCE DB] | mysql --user=[USERNAME]
> --password=[PASSWORD] --
When I perform a dump in mysql5 to mysql 4 DB, I get the error (below).
Does anyone know how I can resolve this?
QUERY (windows server from the cmd prompt)
mysqldump --lock-tables --user=root [SOURCE DB] | mysql --user=[USERNAME]
--password=[PASSWORD] --host=[HOST] [TARGET DB]
ERROR MESS
In the last episode (Feb 22), Ed Curtis said:
> I'm doing the above migration as mentioned in the subject line. I figured I
> would use the MySQL Migration Toolkit to help it along but it won't let me
> connect to my 3.23.49 server. Is there any other way to migrate all my data
> easily.
Basica
On Fri, February 22, 2008 10:01, Ed Curtis wrote:
> I'm doing the above migration as mentioned in the subject line. I
> figured I would use the MySQL Migration Toolkit to help it along but it
> won't let me connect to my 3.23.49 server. Is there any other way to
> migrate all my data easily.
>
> Th
I'm doing the above migration as mentioned in the subject line. I
figured I would use the MySQL Migration Toolkit to help it along but it
won't let me connect to my 3.23.49 server. Is there any other way to
migrate all my data easily.
Thanks,
Ed
--
MySQL General Mailing List
For list archiv
Martjin, I've run various versions of MySQL from 3.2 through 5.1 on various
platforms (Mac OS X, FreeBSD, RedHat/Fedora Linux, Windows, Solaris),
exporting and importing as needed, and haven't encountered any problems.
I've even transferred the MyISAM tables between machines in a few cases,
rather
Dear list,
My company wants to migrate MySQL 5.0.18 from SPARC/Solaris 8 to
Intel/RedHat Enterprise Linux 4 update 4.
Are there any incompatibilities or snags to be expected (expect from the
endian issue, which will be solved by exporting/importing the data)?
Thank you for your time,
Martijn
On 04/01/2007 09:06 AM, Jonathan Horne wrote:
i have a production system running FreeBSD 6.2-p3/MySQL 5.0.33, with 2
databases. i also have a development box, which is pretty much a mirror of my
production system, that i would like to import my databases into. daily, the
production system du
i have a production system running FreeBSD 6.2-p3/MySQL 5.0.33, with 2
databases. i also have a development box, which is pretty much a mirror of my
production system, that i would like to import my databases into. daily, the
production system dumps the databases to .sql files, as well as is a
-DNewDatabasename -hImprovedDatabaseServer --port=3310 -b -C -e "\.
UseThisFileForInput.sql
Tim...
-Original Message-
From: Matthias Henze [mailto:[EMAIL PROTECTED]
Sent: Monday, March 05, 2007 2:30 AM
To: MySQL General
Subject: migrating 4.0 to 5.0
hi,
i've still serious trouble in migrating dat
>> > i've still serious trouble in migrating databases createted with 4.0 to
>> 5.0.
>> > the problems is still the charset. i'm connecting to mysql with php and
>> when
>> > i try to use the 5.0 db german special chars are messed up. afaik 4.0
&g
Am Montag, 5. März 2007 14:35 schrieb Martijn Tonies:
> Hi,
>
> > i've still serious trouble in migrating databases createted with 4.0 to
> 5.0.
> > the problems is still the charset. i'm connecting to mysql with php and
> when
> > i try to use the 5.0 db g
Hi,
> i've still serious trouble in migrating databases createted with 4.0 to
5.0.
> the problems is still the charset. i'm connecting to mysql with php and
when
> i try to use the 5.0 db german special chars are messed up. afaik 4.0 uses
> latin charset and 5.0 utf8 by
On Mon, Mar 05, 2007 at 08:30:13AM +0100, Matthias Henze wrote:
> hi,
>
> i've still serious trouble in migrating databases createted with 4.0 to 5.0.
> the problems is still the charset. i'm connecting to mysql with php and when
> i try to use the 5.0 db german sp
hi,
i've still serious trouble in migrating databases createted with 4.0 to 5.0.
the problems is still the charset. i'm connecting to mysql with php and when
i try to use the 5.0 db german special chars are messed up. afaik 4.0 uses
latin charset and 5.0 utf8 by default. can some
up correct default character set for your MySQL server or change or
add character sets to your definitions of tables and databases in dumped
file
8) load data
HTH
Dusan
- Original Message -
From: "Sean O'Hara" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, March 14, 2006
Hi,
I have figured out a way to get this to work. I am just posting what
I did in case anyone else stumbles across my original message. I am
sure there are other ways to get this to work, but this is the way
that worked for me:
###
# My HOW
Hi,
I am having character set problems while trying to migrate my data
from a server running 4.0.25-standard to a server running 4.1.16. I
believe that the orginal database was using the latin1 character set
(not sure, is there any way to tell? show full column doesn't seem to
be supporte
On Mon, Sep 05, 2005 at 11:00:43AM -0700, Karam Chand wrote:
> First all it is not recommended at all to dump and
> import user information.
Why not? They are just entries in a database, like any other. How
would you propose I move a large batch of users to another database
server?
> Secondly
On Mon, Sep 05, 2005 at 12:41:50PM +0300, Gleb Paharenko wrote:
> Hello.
>
> Have you run 'FLUSH PRIVILEGES'?
Doh! I got everything else find, but forgot something stupid.
Murphy's law, I suppose.
Thanks for the prompt!
Ross
--
MySQL General Mailing List
For list archives: http://lists.mysql
keeps a hash of the password
and all the comparison are done against it.
Karam
--- [EMAIL PROTECTED] wrote:
> Hello everyone,
>
> I'm working on migrating a number of users to a
> different database
> server. mysqldump makes this quite easy, but I've
> run into a
>
Hello.
Have you run 'FLUSH PRIVILEGES'?
[EMAIL PROTECTED] wrote:
> On Sun, Sep 04, 2005 at 10:08:32PM -0400, [EMAIL PROTECTED] wrote:
>> Now I have all the users in the new mysql.user table. But when I try
>> to login, the same credentials do not work.
>
> A bit more info on this. T
On Sun, Sep 04, 2005 at 10:08:32PM -0400, [EMAIL PROTECTED] wrote:
> Now I have all the users in the new mysql.user table. But when I try
> to login, the same credentials do not work.
A bit more info on this. This interesting error happens with GRANT:
mysql> grant all on testing.* to testing@'%'
Hello everyone,
I'm working on migrating a number of users to a different database
server. mysqldump makes this quite easy, but I've run into a
surprising issue with the new server.
I imported things like this:
# mysqldump --skip-add-drop --all-databases | mysql -h newbox -u root -
Wiebe de Jong <[EMAIL PROTECTED]> wrote on 02/09/2005 17:32:07:
> I used mixed case in naming my schemas, tables and fields in Postgres
7.1.
> (i.e. onDemand.callDetailRecord) Now I have to move my app over to
MySQL.
>
>
>
> What are the best practices for naming in MySQL?
Definitely use low
I used mixed case in naming my schemas, tables and fields in Postgres 7.1.
(i.e. onDemand.callDetailRecord) Now I have to move my app over to MySQL.
What are the best practices for naming in MySQL?
Wiebe
,
Adelaide 5000
Australia
+61 8 8408 4273 - Work
+61 417 268 665 - Mobile
+61 8 8408 4259 - Fax
-Original Message-
From: Rahul Bollampally [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 15 June 2005 6:31 AM
To: mysql@lists.mysql.com
Subject: Migrating from IBM Universe to mySQL
Hi,
Has any
Hello,
I guess IBMs Universe Database will be having an ODBC
interface. Then you can use a GUI like SQLyog
(www.webyog.com) to do an ODBC Import from IBMs
database to MySQL.
Regards,
Karam
--- Rahul Bollampally <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Has any body migrated an IBM's Universe databa
Hi,
Has any body migrated an IBM's Universe database to mySQL if so
could you guys please help me out, I need to migrate a huge dataset in
Universe to mySQL to generate an analysis report.
Rahul :-\
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To uns
Message - From: "Brian Erickson"
<[EMAIL PROTECTED]>
To:
Sent: Sunday, May 08, 2005 10:47 PM
Subject: Migrating Database
Greetings all,
We are migrating our web site from one server to another and are
having some issues with transferring our MySQL database. Here's the
Brian Erickson wrote:
>Greetings all,
>
>We are migrating our web site from one server to another and are
>having some issues with transferring our MySQL database. Here's the
>process we're currently using:
>
>1) run mysqldump for each table in our database (i
n" <[EMAIL PROTECTED]>
To:
Sent: Sunday, May 08, 2005 10:47 PM
Subject: Migrating Database
Greetings all,
We are migrating our web site from one server to another and are
having some issues with transferring our MySQL database. Here's the
process we're currently using:
1) run
Greetings all,
We are migrating our web site from one server to another and are
having some issues with transferring our MySQL database. Here's the
process we're currently using:
1) run mysqldump for each table in our database (i.e. one file for each table)
2) compress each file us
can do to protect floats and the like is to use
>mysqldump to dump them to a .sql on the 32 bit system then import them
>again on the 64 bit system.
>
>-Eric
>
>
>On Mon, 4 Oct 2004 16:38:13 -0700 (PDT), alex ye wrote:
> > Does anyone has the experience on migrating mysq
PROTECTED]
Subject: RE: Migrating from Oracle to mySql [online stats]
Hi,
I am also doing migration from oracle 7.3 to mysql 4.0 classic.
May i know how to handle Oracle Views, stored procedures/triggers in MySQL
4.0 ?.
May i know how to create database, table space, roll back segm
Kevin Cowley
R&D
Tel: 0118 902 9099 (direct line)
Email: [EMAIL PROTECTED]
Web: http://www.alchemetrics.co.uk
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: 05 October 2004 16:03
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>
help me how to do this in mysql?.
Thanks,
Narasimha
-Original Message-
From: martin fasani [mailto:[EMAIL PROTECTED]
Sent: Tue 10/5/2004 4:32 PM
To: [EMAIL PROTECTED]
Cc:
Subject: Migrating from Oracle to mySql [online stats
First of all a kind salute to the master yoda of SQL query's Shawn Green :)
He saved me a couple of hours the other day with a linking a table to itself
query !
I've been in the Telecommunications industry for more than 2 years now. I
hope that I can provide feedback any questions regarding DB
kno
thing you can do to protect floats and the like is to use
>mysqldump to dump them to a .sql on the 32 bit system then import them
>again on the 64 bit system.
>
>-Eric
>
>
>On Mon, 4 Oct 2004 16:38:13 -0700 (PDT), alex ye wrote:
> > Does anyone has the experience on migrati
a .sql on the 32 bit system then import them
again on the 64 bit system.
-Eric
On Mon, 4 Oct 2004 16:38:13 -0700 (PDT), alex ye wrote:
> Does anyone has the experience on migrating mysql server from 32bit
sysem to a 64bit system?
> Can data files(from 32bit system) be readed properly by my
u can do to protect floats and the like is to use
mysqldump to dump them to a .sql on the 32 bit system then import them
again on the 64 bit system.
-Eric
On Mon, 4 Oct 2004 16:38:13 -0700 (PDT), alex ye wrote:
> Does anyone has the experience on migrating mysql server from 32bit sysem to a 64bit
&
The safest thing you can do to protect floats and the like is to use
mysqldump to dump them to a .sql on the 32 bit system then import them
again on the 64 bit system.
-Eric
On Mon, 4 Oct 2004 16:38:13 -0700 (PDT), alex ye <[EMAIL PROTECTED]> wrote:
> Does anyone has the experience on
Does anyone has the experience on migrating mysql server from 32bit sysem to a 64bit
system?
Can data files(from 32bit system) be readed properly by mysql server after copy to a
64bit system?
Thank you in advance!
--Alex
__
Do You Yahoo
Subject: Migrating Access Tables -- Empty Columns, Date and Time
I'm migrating a Microsoft Access 2002 (Service Pack 3) table constructed
by my wife to a corresponding table in MySQL 4.0.20. Some columns in
most of the 3000+ rows are empty. Some of these are contiguous empty
columns. I don'
ne 28, 2004 8:21 PM
To: [EMAIL PROTECTED]
Subject: Migrating Access Tables -- Empty Columns, Date and Time
I'm migrating a Microsoft Access 2002 (Service Pack 3) table constructed
by my wife to a corresponding table in MySQL 4.0.20. Some columns in
most of the 3000+ rows are empty. Some of
Bob
My versions are Access 2000 and MySQL 4.0.20. Here's what I do.
When exporting my Access table, I choose the file type Text Files.
Then, on the next dialog box, make sure to click the Advanced button to
get to the formatting information. Change the date order to YMD and the
date delimiter to
I'm migrating a Microsoft Access 2002 (Service Pack 3) table constructed
by my wife to a corresponding table in MySQL 4.0.20. Some columns in
most of the 3000+ rows are empty. Some of these are contiguous empty
columns. I don't know if Access considers them NULL or not, but when you
Hi,
> Hello people ! I was hoping for some wisdom from the good folks on this
> list about moving databases from access to MySQL.
>
> I am aware of the brute force method of exporting in CSV format or tab
> delimited formats and using mysqlimport to move the tables.
>
> 1. I was wondering if there
: Migrating Access databases to MySQL
Hello people ! I was hoping for some wisdom from the good folks on this list
about moving databases from access to MySQL.
I am aware of the brute force method of exporting in CSV format or tab
delimited formats and using mysqlimport to move the tables.
1. I was
Try SQLyog - www.webyog.com
I use the ODBC Import Facility regularly.
regards
Karam
--- Arjun Subramanian <[EMAIL PROTECTED]> wrote:
> Hello people ! I was hoping for some wisdom from the
> good folks on this
> list about moving databases from access to MySQL.
>
> I am aware of the brute force
Arjun Subramanian wrote:
Do you have any
specific sites or utilities in mind ?
Try the code posted in this newsgroup posting:
http://groups.google.com/groups?q=macro+access+export+mysql&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=tchs8rl5phqib7%40corp.supernews.com&rnum=3
It's a little long to post here
d. Are you?"
-Original Message-
From: Bob Ramsey [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 9:07 PM
To: Arjun Subramanian
Subject: Re: Migrating Access databases to MySQL
Arjun Subramanian wrote:
>3. Is there any way other than downloading some shareware third party
>
Hello people ! I was hoping for some wisdom from the good folks on this
list about moving databases from access to MySQL.
I am aware of the brute force method of exporting in CSV format or tab
delimited formats and using mysqlimport to move the tables.
1. I was wondering if there was a way to du
I have MySQL Server 3.23.xx running on RedHat Linux 9 with 40GB
harddrive and 256 RAM. I'm using MyISAM table type with around 157
tables.
I think i decided to change MyISAM table to InnoDB table. But, I don't
know how to do that for the first step. I have read a section on MySQL
documentation abo
Asep Andria I.W. wrote:
I have MySQL Server 3.23.xx running on RedHat Linux 9 with 40GB
harddrive and 256 RAM. I'm using MyISAM table type with around 157
tables.
I think i decided to change MyISAM table to InnoDB table. But, I don't
know how to do that for the first step. I have read a section o
Hi
i am able to use mysqldump as
mysqldump --opt xyz >xyz.sql
i got the file xyz.sql.
i put that file in 4.0.17 directory and ran
bin/mysql -e "source path/xyz.sql"
then it say's
' ERROR 1049: Unknown database 'xyz'
if i try to create this database and try to run the command
Try using the actual MySQL dump command
mysqldump --B --tables -u --opt -p -h |
mysql -u -p -h
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 2/5/04, 10:46:21 AM, UpFront
Hello,
I am trying to copy the "mysql" database to a new MySQL server. I have
tried the mysql dump method:
dump data into a file > mysql2.sql
move file to the new server
execute:
mysql -u root -p -e "source mysql2.sql" mysql -on the new server
I con
We run Tomcat4. Currently we are using the older mm- drivers. Is there
anyway to move to connector /J one context at a time rather than all at
once?
William R. Mussatto, Senior Systems Engineer
Ph. 909-920-9154 ext. 27
FAX. 909-608-7061
--
MySQL General Mailing List
For list archives: http:/
Timothy Stone <[EMAIL PROTECTED]> wrote:
> Okay, don't cut my head off. MySQL is new for me, but I'm not new to
> databases.
>
> I have a MySQL DB for development running on WinNT (3.23.51-max-nt). I'm
> migrating the database for development to Mac OS X M
Okay, don't cut my head off. MySQL is new for me, but I'm not new to
databases.
I have a MySQL DB for development running on WinNT (3.23.51-max-nt). I'm
migrating the database for development to Mac OS X MySQL 4.0.12.
I've read both the "Upgrading From v3.23 to
gt;
Sent: Tuesday, February 11, 2003 4:54 PM
Subject: Migrating Microsoft Access to MySQL
> I am with a small business in Southern California that would like to
migrate
> our MS Access databases to MySQL server. Are their any computer se
1 - 100 of 137 matches
Mail list logo
