I have experimented only with replication. All of my experimentation has
been on two machines on the same physical network. I quickly determined
that replication was not going to be a good solution for what I wanted: An
always available inquiry server (free from lock conflicts caused by long
running updates). This proved not to work in my tests because it seems that
what is logged (and therefore replicated) is only the query which performed
the update which takes just as long to run on the replicated server as it
did on the master (causing the same blocking problems).
This together with the lengthy "known problems with replication" section of
the manual and the frequent "replication problem" postings to this group has
left me with the impression that this feature is not exactly ready for
prime-time.
I think your 2-way replication idea is a non-starter. I believe that the
manual is very clear that mysql provides one-way only replication. I don't
believe that it is even possible to configure a server as both a master and
a slave. Even if you could, it seems likely that you would end up with an
infinite loop.
> -----Original Message-----
> From: Neil Tompkins [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, September 22, 2001 1:49 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Backup Data
>
>
> Thanks for your reply. What about replication ? I've looked at this, but
> everyone says read the manual. I would like to hear from someone who has
> had experience with this and does it work correctly.
>
> For example has anyone had a database online with a ISP and
> updated a local
> copy locally with any changes being replicated to the ISPs copy.
> Also, has
> anyone made changes online and then replicate these changes back to the
> local copy e.g two way replication
>
> Thanks
> Neil
>
> ----- Original Message -----
> From: "Will French" <[EMAIL PROTECTED]>
> To: "Neil Tompkins" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Saturday, September 22, 2001 6:45 PM
> Subject: RE: Backup Data
>
>
> > There are two methods that I commonly use to move data from mySql into
> > Access.
> >
> > The first is to use a myODBC connection and simply import the tables.
> Given
> > the size of your database (small that is) this would be quite quick
> assuming
> > that you are able to establish an ODBC connection to your
> database accross
> > the net (I bet you can). If you haven't already, you should dl and
> install
> > myODBC. Be warned though, if your database is large (many of my tables
> have
> > > 1 million records) this method of import can be quite slow (even for
> > Access).
> >
> > The second method is select your files into "OUTFILE"s and then import
> them
> > into Access using the text import wizard. The select statement
> would look
> > something like this:
> > SELECT * INTO OUTFILE '<put your filename here>'
> > FROM <put your table name here>
> > Note: If your table contains binary data, you won't be able to use this
> > method.
> >
> > The second method is generally quicker but has a couple of downsides:
> > - It will not create your table definition for you! You will have to
> > either:
> > 1. pre-define your table and then import into it
> > 2. define your table through the import-text wizard (see the advanced
> > button)
> > 3. import it and then go back and massage the field definitions.
> > - For options 2 and 3 be carefull! Access only scans so many rows (50?)
> to
> > decide what type to assign an import field. This often leads to import
> > errors. Also note that Access will always default text fields
> to a length
> > of 255 which may cause unnecessary overhead if your fields are in fact
> > smaller (and most, of course, are).
> >
> > Because Access' table definition is pretty time consuming to use, I
> > sometimes first do a "SHOW COLUMNS" into a text file and then
> use EXCEL to
> > massage that result set into a CREATE TABLE DDL query (many people don't
> > know that Access supports DDL queries). After I have the table
> set up, I
> > import into that table.
> >
> > > -----Original Message-----
> > > From: Neil Tompkins [mailto:[EMAIL PROTECTED]]
> > > Sent: Saturday, September 22, 2001 1:11 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Backup Data
> > >
> > >
> > > Hello,
> > >
> > > I currently have about 2500 records in a mySQL database that is
> > > hosted with
> > > my ISP. I am very familar with MS Access. Is it possible that I
> > > can backup
> > > my data into a MS Access database ? Any advice would be very
> grateful !
> > >
> > > Thanks
> > >
> > > Neil
> > > www.advertising-online.net
> > >
> > > ---------------------------------------------------------------------
> > > 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
> > >
> > >
> >
> >
>
> ---------------------------------------------------------------------
> 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
>
>
---------------------------------------------------------------------
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
