MySQL Bugs: #70170: Database with dot "." in name gets split.

Bug #70170	Database with dot "." in name gets split.
Submitted:	27 Aug 2013 21:32	Modified:	6 Nov 2013 0:26
Reporter:	Adam Yhap	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Migration	Severity:	S3 (Non-critical)
Version:	6.0.6.11184	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	microsoft, migrate, ms sql, MSSQL, MySQL, split

Description:
I am trying to migrate from MS SQL to MySQL. Our database names have periods in them.

When run trying to migrate, the name are being split.

How to repeat:
Create a database on sql server with a "." in the name.

Try to migrate to mysql.

Thank you for the bug report.

Here's a diff file with the patch to fix this bug

Attachment: fixes_bug_70170.diff (text/x-patch), 8.82 KiB.

Thanks for jumping on this so quickly. The wizard now reads the schema correctly.

When workbench tries to reverse engineer, it throws the following error:

ERROR: Reverse engineer selected schemata: ProgrammingError("('42S02', "[42S02] [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid object name 'INFORMATION_SCHEMA.TRIGGERS'. (208) (SQLExecDirectW); [42000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Statement(s) could not be prepared. (8180)")"): error calling Python module function DbSql92RE.reverseEngineer

Failed

Could this be related?

Forgive me, our database is not SQL92 compliant. However, using Generic RDBMS gives the this error. 

Let 'Lorem.Ipsum' be default database.

ERROR: Retrieve schema list from source: ProgrammingError("('42000', "[42000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Could not find server 'Lorem' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers. (7202) (SQLTables)")"): error calling Python module function DbGenericRE.getSchemaNames
Failed

Posted by developer:
 
FIXED.
Verified in:
Windows 7x64
Ubuntu 12.04x64
MySQL Server 5.6
MSSQL Server 2008
WB 6.0.8.11345
Migration of a DB or table with "." within the name is sucessfull.
NOTE: The "." character is substituted by a "_".

II. Data Copy

  - `Bug Spaces`.`table_with spaces`

            Succeeded : copied 4 of 4 rows from [Bug Spaces].[dbo].[table.with spaces]

Fixed as of MySQL Workbench 6.0.8, and here's the changelog entry:

While migrating a Microsoft SQL Server database to MySQL, database names
with periods would fail, and now the periods are replaced with
underscores. For example, "foo.bar" will become "foo_bar".

Thank you for the bug report.