Bug #39530 Migrate database from SQL Server to MYSQL

• Submitted: 19 Sep 2008 7:17
• Modified: 19 Oct 2008 14:22
• Reporter: h h
• Status: No Feedback
• Category: MySQL Migration Toolkit
• Severity: S2 (Serious)
• Version: 3.51.22
• OS: Windows (sp3)
• CPU Architecture: Any
• Tags: migration

[19 Sep 2008 7:17] h h

Description:
I'm trying to migrate database from SQL Server to MYSQL. Ofcouse the, script need to custumize too. But for this error im stuck already. Unknown
system variable "CONCAT_NULL_YIELDS_NULL". Here is error msg and sql in SQL Server:

Microsoft OLE DB Provider for ODBC Drivers error '80040e21' 
ODBC driver does not support the requested properties. 

SET CONCAT_NULL_YIELDS_NULL OFF SELECT DISTINCT sect_code_1 + ' ' + ( 
SELECT sect_desc
FROM section
WHERE sect_code = sect_code_1 ) + '~' + sect_code_2 + ' ' + ( 
SELECT sect_desc
FROM section
WHERE sect_code = sect_code_2 ) + '~' + sect_code_3 + ' ' + ( 
SELECT sect_desc
FROM section
WHERE sect_code = sect_code_3 ) + '~' + sect_code_4 + ' ' + ( 
SELECT sect_desc
FROM section
WHERE sect_code = sect_code_4 ) + '~' + sect_code_5 + ' ' + ( 
SELECT sect_desc
FROM section
WHERE sect_code = sect_code_5 ) + '~' + sect_code_6 + ' ' + ( 
SELECT sect_desc
FROM section
WHERE sect_code = sect_code_6 ) + '~' + sect_code_7 + ' ' + ( 
SELECT sect_desc
FROM section
WHERE sect_code = sect_code_7 ) + '~' + sect_code_8 + ' ' + ( 
SELECT sect_desc
FROM section
WHERE sect_code = sect_code_8 ) + '~' + sect_code_9 + ' ' + ( 
SELECT sect_desc
FROM section
WHERE sect_code = sect_code_9 ) + '~' + sect_code_10 + ' ' + ( 
SELECT sect_desc
FROM section
WHERE sect_code = sect_code_10 ) + '~' AS sect_str
FROM proc_sect_rel
ORDER BY sect_str

Thanks in advance.

How to repeat:
This sql wil list out a tree menu. So, is it there is a function similar to "CONCAT_NULL_YIELDS_NULL OFF".

[19 Sep 2008 14:22] MySQL Verification Team

Thank you for the bug report. Are you able to provide a test case script?. Thanks in advance.

[19 Oct 2008 23:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".