Converting MS SQL to MySQL

Hey there :)

I'm in a project to build an eCommerce site using TYPO3. We've been trying
to get everything up and running on a Windows + IIS + MS SQL setup (for
political reasons), which has proven to be very problematic. Actually,
we're at the point were we pretty much have to switch to MySQL for things
to work out.

Thing is, we already have a 43-table 15+ GB MS SQL database with commerce
items that we need to migrate to the MySQL server. There are no stored
procedures, but there are a handful of Views (I don't think we really need
them), and relations exist in some form within the database (I know nothing
of the workings of MS SQL myself, and unfortunately, my boss and creator of
the database is currently in Malaysia, so you'll have to bear with me in
being a bit unspecific, sorry).

Do you have any recommendations on how to (relatively) easily replicate the
MS SQL database to a new MySQL database? I have installed MySQL 5 on the
same server that holds the MS SQL server. Next up is to "convert" it.
Needless to say, it'd be nice to do this "the right way", whichever way
that really is :)

Thanks in advance for any help,
Daniel Buus

Daniel Smedegaard Buus wrote:

> Hey there :)
>
> I'm in a project to build an eCommerce site using TYPO3. We've been trying
> to get everything up and running on a Windows + IIS + MS SQL setup (for
> political reasons), which has proven to be very problematic. Actually,
> we're at the point were we pretty much have to switch to MySQL for things
> to work out.
>
> Thing is, we already have a 43-table 15+ GB MS SQL database with commerce
> items that we need to migrate to the MySQL server. There are no stored
> procedures, but there are a handful of Views (I don't think we really need
> them), and relations exist in some form within the database (I know
> nothing of the workings of MS SQL myself, and unfortunately, my boss and
> creator of the database is currently in Malaysia, so you'll have to bear
> with me in being a bit unspecific, sorry).
>
> Do you have any recommendations on how to (relatively) easily replicate
> the MS SQL database to a new MySQL database? I have installed MySQL 5 on
> the same server that holds the MS SQL server. Next up is to "convert" it.
> Needless to say, it'd be nice to do this "the right way", whichever way
> that really is :)
>
> Thanks in advance for any help,
> Daniel Buus


Have a look at
http://www.mysql.com/why-mysql/white...ssql2mysql.php

--
Brian Wakem
Email: http://homepage.ntlworld.com/b.wakem/myemail.png

Hello Daniel,

> I'm in a project to build an eCommerce site using TYPO3. We've been trying
> to get everything up and running on a Windows + IIS + MS SQL setup (for
> political reasons), which has proven to be very problematic. Actually,
> we're at the point were we pretty much have to switch to MySQL for things
> to work out.
>
> Thing is, we already have a 43-table 15+ GB MS SQL database with commerce
> items that we need to migrate to the MySQL server. There are no stored
> procedures, but there are a handful of Views (I don't think we really need
> them), and relations exist in some form within the database (I know
nothing
> of the workings of MS SQL myself, and unfortunately, my boss and creator
of
> the database is currently in Malaysia, so you'll have to bear with me in
> being a bit unspecific, sorry).
>
> Do you have any recommendations on how to (relatively) easily replicate
the
> MS SQL database to a new MySQL database? I have installed MySQL 5 on the
> same server that holds the MS SQL server. Next up is to "convert" it.
> Needless to say, it'd be nice to do this "the right way", whichever way
> that really is :)

Depending on what you actually used in MS SQL, many things will convert
just fine.

There are tools that allow you to convert tables/indices/constraints, for
example,
our tool: Database Workbench and it's Schema Migrator ( www.upscene.com )

Of course, it's possible that some things won't get converted, like certain
features
in TSQL (functions or so) in your views.


--
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com

Martijn Tonies wrote:

> Hello Daniel,
>
>> I'm in a project to build an eCommerce site using TYPO3. We've been
>> trying to get everything up and running on a Windows + IIS + MS SQL setup
>> (for political reasons), which has proven to be very problematic.
>> Actually, we're at the point were we pretty much have to switch to MySQL
>> for things to work out.
>>
>> Thing is, we already have a 43-table 15+ GB MS SQL database with commerce
>> items that we need to migrate to the MySQL server. There are no stored
>> procedures, but there are a handful of Views (I don't think we really
>> need them), and relations exist in some form within the database (I know
> nothing
>> of the workings of MS SQL myself, and unfortunately, my boss and creator
> of
>> the database is currently in Malaysia, so you'll have to bear with me in
>> being a bit unspecific, sorry).
>>
>> Do you have any recommendations on how to (relatively) easily replicate
> the
>> MS SQL database to a new MySQL database? I have installed MySQL 5 on the
>> same server that holds the MS SQL server. Next up is to "convert" it.
>> Needless to say, it'd be nice to do this "the right way", whichever way
>> that really is :)
>
> Depending on what you actually used in MS SQL, many things will convert
> just fine.
>
> There are tools that allow you to convert tables/indices/constraints, for
> example,
> our tool: Database Workbench and it's Schema Migrator ( www.upscene.com )
>
> Of course, it's possible that some things won't get converted, like
> certain features
> in TSQL (functions or so) in your views.
>
>

Hi Martijn, thanks for replying!

Thanks for the link, too. At the moment, the database is being copied by
using the DTS thing in SQL Server 2000, via MySQL ODBC 3.51. We haven't
really decided yet whether or not we're going to migrate for good, because
the primary decision maker is in Malaysia until Monday. But, depending on
the outcome, we may need proper conversion tools, so thanks for the link :)

Cheers,
Daniel

Brian Wakem wrote:

> Daniel Smedegaard Buus wrote:
>
>> Hey there :)
>>
>> I'm in a project to build an eCommerce site using TYPO3. We've been
>> trying to get everything up and running on a Windows + IIS + MS SQL setup
>> (for political reasons), which has proven to be very problematic.
>> Actually, we're at the point were we pretty much have to switch to MySQL
>> for things to work out.
>>
>> Thing is, we already have a 43-table 15+ GB MS SQL database with commerce
>> items that we need to migrate to the MySQL server. There are no stored
>> procedures, but there are a handful of Views (I don't think we really
>> need them), and relations exist in some form within the database (I know
>> nothing of the workings of MS SQL myself, and unfortunately, my boss and
>> creator of the database is currently in Malaysia, so you'll have to bear
>> with me in being a bit unspecific, sorry).
>>
>> Do you have any recommendations on how to (relatively) easily replicate
>> the MS SQL database to a new MySQL database? I have installed MySQL 5 on
>> the same server that holds the MS SQL server. Next up is to "convert" it.
>> Needless to say, it'd be nice to do this "the right way", whichever way
>> that really is :)
>>
>> Thanks in advance for any help,
>> Daniel Buus
>
>
> Have a look at
> http://www.mysql.com/why-mysql/white...ssql2mysql.php
>

Thank you, Martin, for this link! The paper will surely come in handy,
especially to the DBA.

Cheers,
Daniel

Daniel Smedegaard Buus wrote:

> Brian Wakem wrote:
>
>> Daniel Smedegaard Buus wrote:
>>
>>> Hey there :)
>>>
>>> I'm in a project to build an eCommerce site using TYPO3. We've been
>>> trying to get everything up and running on a Windows + IIS + MS SQL
>>> setup (for political reasons), which has proven to be very problematic.
>>> Actually, we're at the point were we pretty much have to switch to MySQL
>>> for things to work out.
>>>
>>> Thing is, we already have a 43-table 15+ GB MS SQL database with
>>> commerce items that we need to migrate to the MySQL server. There are no
>>> stored procedures, but there are a handful of Views (I don't think we
>>> really need them), and relations exist in some form within the database
>>> (I know nothing of the workings of MS SQL myself, and unfortunately, my
>>> boss and creator of the database is currently in Malaysia, so you'll
>>> have to bear with me in being a bit unspecific, sorry).
>>>
>>> Do you have any recommendations on how to (relatively) easily replicate
>>> the MS SQL database to a new MySQL database? I have installed MySQL 5 on
>>> the same server that holds the MS SQL server. Next up is to "convert"
>>> it. Needless to say, it'd be nice to do this "the right way", whichever
>>> way that really is :)
>>>
>>> Thanks in advance for any help,
>>> Daniel Buus
>>
>>
>> Have a look at
>> http://www.mysql.com/why-mysql/white...ssql2mysql.php
>>
>
> Thank you, Martin, for this link! The paper will surely come in handy,
> especially to the DBA.
>
> Cheers,
> Daniel


No problem, but my name's Brian.


--
Brian Wakem
Email: http://homepage.ntlworld.com/b.wakem/myemail.png