Subject | Re: MySQL DB-->Firebird |
---|---|
Author | David K. |
Post date | 2005-03-28T17:21:23Z |
I should also mention that I am running on Windows XP SP2. That file
does not install on my system :-)
does not install on my system :-)
--- In IB-Conversions@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
> At 04:42 AM 28/03/2005 +0000, David K. wrote:
>
> >I'm very new to this and am wondeirng if this is the right place to
> >post and ask.
> >I am using a program called SAM from spacialaudio.com and I would like
> >to completely move away from MYSQL, and use FireBird. How do I import
> >the SAMDB from MySQL into FireBird?
>
> See http://www.clevercomponents.com/products/datapump/dp-tour.asp
>
> Since (as you say) you are very new to this and you don't say where
you are
> standing with respect to the software (end-user? developer?
developer of
> third-party products that use SAM?) then don't look for a miracle. For
> example, migrating data from a database in the *format* used by one
DBMS to
> the *format* used by another is relatively simple, i.e. a way can
usually
> be found to do it.
>
> What may matter more for a DBMS at the back-end of an existing software
> product is the way data is managed. MySQL isn't useful for
client/server
> systems that need bomb-proof control of multiple concurrent read-write
> clients; on the other hand, it is ideal for back-ending software that
> needs load-once, read often data storage. That characteristic might
well
> be why the SAM developer chose MySQL at all...
>
> As a SAM user, there would be a number of essential issues to
understand
> before committing yourself to your plan, including:
>
> 1) Does it need/can it work with concurrency support? If so, do you
have
> the means to manipulate transactions from your user/developer interface?
> 2) Does your software/interface depend on MySQL-specific data types
like
> identity or Boolean?
> 3) Is data integrity tightly bound to application code as, with
MySQL, it
> necessarily is?
> 4) ...and more...
>
> All this is NOT to discourage you from experimenting with Firebird.
Take a
> copy of your MySQL database and just go for it. Even if you end up
with a
> database that your software doesn't like, you will have in your hand
your
> own personal Firebird database on which to cut your DBA teeth. If
we are
> all lucky, you will chronicle your experiences (failures and successes
> alike) and have a HowTo that is sure to give someone else a
much-need leg-up.
>
> Helen