Import MySQL Backup to MS SQL Server

"Tibor Karaszi" wrote in
message

> Run the SQL scripts using SSMS, or SQLCMD? But you first need to handle
> whatever SQL in there which isn't compatible with SQL Server.

I kind of figured that much. But this produces a lot of errors and, at
161MB, it seems like it would take forever to edit the file by hand.

I just wondered if anyone had created an automated way of doing this.

Jonathan
 >> Stay informed about: Import MySQL Backup to MS SQL Server 

> I just wondered if anyone had created an automated way of doing
> this.

I see. I gooled for below and it seems there are tools and such out
there:
"mySQL to SQL Server"

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Jonathan Wood" wrote in message

> "Tibor Karaszi"
> wrote in message
>
>> Run the SQL scripts using SSMS, or SQLCMD? But you first need to
>> handle whatever SQL in there which isn't compatible with SQL
>> Server.
>
> I kind of figured that much. But this produces a lot of errors and,
> at 161MB, it seems like it would take forever to edit the file by
> hand.
>
> I just wondered if anyone had created an automated way of doing
> this.
>
> Jonathan
>
 >> Stay informed about: Import MySQL Backup to MS SQL Server 

Thanks, I'm checking that out. Nothing looks really good yet and I have the
option of discarding the data and starting again. I didn't want to discard
the data but it's sounding like a better and better option all the time. <g>

BTW, the MySQL script contains very long lines which makes the SSMS editor
take about 20 seconds virtually every time I move the cursor. Trying to edit
the file directly there is out of the question.

Jonathan

"Tibor Karaszi" wrote in
message
>> I just wondered if anyone had created an automated way of doing this.
>
> I see. I gooled for below and it seems there are tools and such out there:
> "mySQL to SQL Server"
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
>
> "Jonathan Wood" wrote in message
>
>> "Tibor Karaszi" wrote
>> in message
>>
>>> Run the SQL scripts using SSMS, or SQLCMD? But you first need to handle
>>> whatever SQL in there which isn't compatible with SQL Server.
>>
>> I kind of figured that much. But this produces a lot of errors and, at
>> 161MB, it seems like it would take forever to edit the file by hand.
>>
>> I just wondered if anyone had created an automated way of doing this.
>>
>> Jonathan
>>
>
>
 >> Stay informed about: Import MySQL Backup to MS SQL Server 

Jonathan Wood (jwood@softcircuits.com) writes:
> Thanks, I'm checking that out. Nothing looks really good yet and I have
> the option of discarding the data and starting again. I didn't want to
> discard the data but it's sounding like a better and better option all
> the time. <g>
>
> BTW, the MySQL script contains very long lines which makes the SSMS
> editor take about 20 seconds virtually every time I move the cursor.
> Trying to edit the file directly there is out of the question.

Just because it's SQL, you don't have to edit it SSMS. Textpad, for instance
works a lot better with long lines. (www.textpad.com). And you can set up
a command-line tool in Textpad, so you can pass the file to SQLCMD.

Although I will have to admit that I would not take up such an editing
task myself.

--
Erland Sommarskog, SQL Server MVP, esquel.DeleteThis@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
 >> Stay informed about: Import MySQL Backup to MS SQL Server 

"Erland Sommarskog" wrote in message


>> Thanks, I'm checking that out. Nothing looks really good yet and I have
>> the option of discarding the data and starting again. I didn't want to
>> discard the data but it's sounding like a better and better option all
>> the time. <g>
>>
>> BTW, the MySQL script contains very long lines which makes the SSMS
>> editor take about 20 seconds virtually every time I move the cursor.
>> Trying to edit the file directly there is out of the question.
>
> Just because it's SQL, you don't have to edit it SSMS. Textpad, for
> instance
> works a lot better with long lines. (www.textpad.com). And you can set up
> a command-line tool in Textpad, so you can pass the file to SQLCMD.

Yes, I realize that. I loaded it into a more efficient program initially to
see what was there. However, the syntax coloring really helps when you've
got multi-million character lines and somewhere between the start and end of
those lines it got confused about what was inside and what was outside of
the single quotes.

> Although I will have to admit that I would not take up such an editing
> task myself.

Heh, I think that makes two of us.

Jonathan
 >> Stay informed about: Import MySQL Backup to MS SQL Server 

Jonathan Wood (jwood@softcircuits.com) writes:
> Yes, I realize that. I loaded it into a more efficient program initially
> to see what was there. However, the syntax coloring really helps when
> you've got multi-million character lines and somewhere between the start
> and end of those lines it got confused about what was inside and what
> was outside of the single quotes.

Third-party text editors typically provide syntax colouring one way or
another.


--
Erland Sommarskog, SQL Server MVP, esquel.RemoveThis@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
 >> Stay informed about: Import MySQL Backup to MS SQL Server 

First: I don't have any valid answer.

I have a 9Gb mysql dump and because of the single quotes and the huge size,
it can't be opened in sql enterprise manager nor edited.

So for now I have a temporary workaround where I have a mysql box running on
windows where I extract the dump, and then I do a dts import from that box to
my sql server. it's not pretty, but works well.

I'm still looking for that magic bullet though.


"Erland Sommarskog" wrote:

> Jonathan Wood (jwood@softcircuits.com) writes:
> > Yes, I realize that. I loaded it into a more efficient program initially
> > to see what was there. However, the syntax coloring really helps when
> > you've got multi-million character lines and somewhere between the start
> > and end of those lines it got confused about what was inside and what
> > was outside of the single quotes.
>
> Third-party text editors typically provide syntax colouring one way or
> another.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel DeleteThis @sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
 >> Stay informed about: Import MySQL Backup to MS SQL Server