Quantcast
Channel: MySQL Forums - MySQL Workbench - Database Migration
Viewing all 560 articles
Browse latest View live
↧

Newbie with a Syntax error (3 replies)

April 11, 2013, 3:38 am
$
0
0
I am getting a syntax error on the last line of this Table statement. Using MySQL. If this is the wrong forum, please let me know:

CREATE TABLE Employees
(firstname VARCHAR(20),
lastname VARCHAR(20),
department VARCH.AR(20),
hiredate DATE,
supervisor INT CHECK (supervisor>1000 AND supervisor<2000),
id INT PRIMARY KEY CHECK (id>1000 AND id<3000));
↧
Search

Datamigration from OPENBIZ Box to Magento (no replies)

October 24, 2012, 9:32 am
$
0
0
Dear Forum,

I have a problem with the migration from a database (Webshop OPENBIZ Box) to a Magento System.

I hope, it is possible to transfer all information with the workbench, has anyone of you experience with this?


Stefan
↧
↧

Data migration error (Reverse engineering process) (no replies)

April 25, 2013, 5:15 am
$
0
0
I am geeting error when iporting the ms sql server 2005 data in mysql.
The error is :
tarting...

Connect to source DBMS...

- Connecting...

Connect to source DBMS done

Reverse engineer selected schemata....

Reverse engineering dbo, VSM from VSM

- Reverse engineering catalog information

- Reverse engineering User Data Types...

- Preparing...

- Gathered stats for dbo

- Gathered stats for VSM

Reverse engineering 145 tables from dbo

- Retrieving table dbo.Delhi_client20a...

- Retrieving table dbo.gridih_associates_15march...

- Retrieving table dbo.Delhi_client20ab...

- Retrieving table dbo.associate2b...

- Retrieving table dbo.gridih_associates_15marcha...

- Retrieving table dbo.gridihtrust_15march...

- Retrieving table dbo.gridihtrust_15marcha...

- Retrieving table dbo.Associate2...

- Retrieving table dbo.DELHI_MEMBER20a...

- Retrieving table dbo.gridih_ltd_15marcha...

- Retrieving table dbo.Gridih19march_assco...

- Retrieving table dbo.Delhi_associate20a...

- Retrieving table dbo.RATES...

- Retrieving table dbo.Relation...

- Retrieving table dbo.Gridih19march_trust...

- Retrieving table dbo.Delhi_associate20ab...

- Retrieving table dbo.Delhi_client20abc...

- Retrieving table dbo.Delhi_member_19abcd...

- Retrieving table dbo.branch1...

- Retrieving table dbo.'TRUST CUSTOMER$'...

Traceback (most recent call last):

File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\db_mssql_grt.py", line 384, in reverseEngineer

reverseEngineerTables(connection, schema)

File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\db_mssql_grt.py", line 557, in reverseEngineerTables

reverseEngineerTablePK(connection, table)

File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\db_mssql_grt.py", line 687, in reverseEngineerTablePK

pk_col_names = [ row[3] for row in execute_query(connection, query) ]

File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\db_mssql_grt.py", line 62, in execute_query

return get_connection(connection_object).cursor().execute(query, *args, **kwargs)

pyodbc.ProgrammingError: ('42000', "[42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near 'TRUST'. (102) (SQLExecDirectW)")



Traceback (most recent call last):

File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\workbench\wizard_progress_page_widget.py", line 192, in thread_work

self.func()

File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\migration_schema_selection.py", line 160, in task_reveng

self.main.plan.migrationSource.reverseEngineer()

File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\migration.py", line 332, in reverseEngineer

self.state.sourceCatalog = self._rev_eng_module.reverseEngineer(self.connection, self.selectedCatalogName, self.selectedSchemataNames, self.state.applicationData)

SystemError: ProgrammingError("('42000', "[42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near 'TRUST'. (102) (SQLExecDirectW)")"): error calling Python module function DbMssqlRE.reverseEngineer

ERROR: Reverse engineer selected schemata: ProgrammingError("('42000', "[42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near 'TRUST'. (102) (SQLExecDirectW)")"): error calling Python module function DbMssqlRE.reverseEngineer

Failed

Could anyone help.
↧

MySQL Workbench 6.0: BETA 1 released (no replies)

June 13, 2013, 6:44 pm
↧

Hangs during reverse engineering (1 reply)

June 18, 2013, 1:18 pm
$
0
0
Hi,

I have following OS configuration

OS : on windows 7 - 64 bit platform with IIS feature installed


I have downloaded and installed mysql-workbench-gpl-5.2.47-win32.

Trying to migrate using mysql workbench :

goal : migrate access database(.mdb files mapped through ODBC connection) to Mysql

Source database : ODBC data source ( connection succeed )
Target databsae : Mysql ( Connection succeed )


During migration processing got hanged at reverse engineering process stage.

Please suggest me your valuable information.

thanks,
dhanjee
↧
↧

Migration Recovery (1 reply)

June 18, 2013, 1:14 pm
$
0
0
I am using MySql Workbench to migrate from MS SQL Server 2005 to MySQL 5.1.39.

I use the batch file created from the tool to copy the different tables.
If any problem occurs during the copy of a very large table is it possible resume copying from the point where it stopped ?

Thanks
↧

Workbench 6 beta: import fails (3 replies)

June 19, 2013, 4:32 am
$
0
0
Experimenting with Workbench 6.0.2 beta on Windows 7 Pro, 32-bit, sp1. Mysql engine is 5.6.10 Did an export and dropped schemas. On data import in the workbench, the first SQL statement begins and hangs. Clicking on stop yields exitcode 1.

I can run the first sql file in the dumps folder in workbench just fine. How best to get the remainder run? Return to Workbench 5?

George
↧

exporting database (1 reply)

June 22, 2013, 4:17 pm
$
0
0
Hello,
I have workbench 5.2.47

I want to export my database via workbench, but I getting an error:

2:49:32 Dumping @@@@ (logins)

Running: "C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqldump.exe" --defaults-extra-file="@@@@.cnf" --user=root --max_allowed_packet=1G --host=localhost --port=3306 --default-character-set=utf8 --no-data "@@@" "logins"

mysqldump: Couldn't execute 'SELECT @@GTID_MODE': Unknown system variable 'GTID_MODE' (1193)

Of some workarround, I realized that for workbench version the new 'GT ID_MODE' doesn't exist (from mysql 5.6), so there is need to add to command line: –-set-gtid-purged=OFF

A problem - I don't know how to change the command line, since *.cnf file is located on temporary folder (I persume it is built when running export via workbench).

Also, it would be better if there is any declaration on some ini file of workbench, that make "gtid-purged=OFF".

Is there also a hotfix for workbench for that?

Thanks :)
↧
Search

How-To: Database Migration from Sybase SQLAnywhere using MySQL Workbench (no replies)

June 25, 2013, 12:53 pm
↧
↧

sql server to mysql for magento (2 replies)

July 1, 2013, 7:29 am
$
0
0
I'm working on restructuring of an existing asp & sql server based online store to magento. I have no knowledge of existing sql server db as it was created by someone else 10 years ago. Which tool i can use to convert whole sql server db or required data from it to magento mysql.

Please help.
↧

workbench encode migration problem. HELP (7 replies)

June 28, 2013, 8:51 am
$
0
0
Hello guys, Argentinian Developer here. I really need help so im hopping you help me with this..

im using this post as last chance since i've spent more than 2 days trying to find a workaround with no luck.

MY GOAL:

To migrate a SQL SERVER DataBase with data to a MySQL version using Workbench


THE CONTEXT:

DB source is on a Microsoft SQL Server Developer Edition. version: 9.00.1399.06

Server Collation is set to SQL_Latin1_General_CP1_CI_AS

I've changed the DB i wanna migrate to Modern_Spanish_CI_AS

In the other hand.. i have MySQL server 5.5.24 version.

So.. i installed MySQL Workbench 5.2.47 in my Windows 7 Ultimate 64bits


THE PROBLEM:

If i go normal way with Migration Wizard it uses Utf8_general_ci to replicate the schema and do bulkcopy so all my string columns are cutted as soon as they find a "spanish" character.

Example:

Mi cabeza tiene un moño rojo -> Mi cabeza tiene un mo


WHAT I'VE TRIED WITHOUT SUCCESS:


I've managed to get the complete strings editing manually the MySQL collation from where objects are made. that's in the first step, the schema replication.

So i've simply replaced utf8_general_ci with latin1_spanish_ci so all my DB and tables are now in a different collation when the schema is made.

but after the bulkcopy now my strings are converted as follows:

Mi cabeza tiene un moño rojo -> Mi cabeza tiene un mo?o rojo

(same happens with áéíóú etc, etc.)


My guess is i gotta change the encode workbench is using to migrate data since if i read the log after proccessing it says it used utf8_general_ci to transfer data (even when i change the schema object collations from manual editing)

I read the workbench manual and it says something about that but the information is so old, those files .PDF are telling me to edit dont event exist anymore !

Im pretty sure im not the only one trying to find a quick way to solve this. So you'll be helping a bunch of people !

Thanks and regards
↧

Sql2005 migration utf8mb4 problem (1 reply)

July 1, 2013, 5:29 am
$
0
0
I really need help for Sql2005 migration problem.

MY GOAL:
To migrate many Sql2005 DataBases with data to a MySQL version 5.6 using Workbench.

Sql2005 DataBases COLLATE is Chinese_PRC_CI_AS.
MySQL Workbench Version 6.0.2 beta.


The Sql2005 DataBases contain some 4 bytes UTF-8.

When Mysql use utf8 collate, Get Error: during charset conversion of wstring: No error.

So i select mysql collate utf8mb4.

+--------------------------+--------------------+
| Variable_name | Value |
+--------------------------+--------------------+
| character_set_client | utf8mb4 |
| character_set_connection | utf8mb4 |
| character_set_database | utf8mb4 |
| character_set_filesystem | binary |
| character_set_results | utf8mb4 |
| character_set_server | utf8mb4 |
| character_set_system | utf8 |
| collation_connection | utf8mb4_general_ci |
| collation_database | utf8mb4_general_ci |
| collation_server | utf8mb4_general_ci |
+--------------------------+--------------------+

modify ther db_mssql_migration_grt.py

def migrateCharsetCollation(self, state, charset, collation, source_object, target_object):
if collation:
state.addMigrationLogEntry(0, source_object, target_object,
'Collation %s migrated to utf8_general_ci' % (collation))
return '', 'utf8_general_ci'

return charset, collation


as:

def migrateCharsetCollation(self, state, charset, collation, source_object, target_object):
if collation:
state.addMigrationLogEntry(0, source_object, target_object,
'Collation %s migrated to utf8mb4_general_ci' % (collation))
return '', 'utf8mb4_general_ci'

return charset, collation

When migrate also get Error: during charset conversion of wstring: No error.


How to migrate Sql2005 DataBases which have some 4 bytes UTF-8 to a MySQL?

Thanks and regards.
↧

Sybase to MySQL (3 replies)

July 8, 2013, 12:13 pm
$
0
0
We have several flavors of databases where I work and they all talk to each other. Currently, we have a Sybase database talking to a MySQL database. MySQL is the destination. To make a long story short, I need to "re-seed" the data on MySQL with data from Sybase. Here is what I am going to do.

The table in question is using the MyISAM engine.

1. BCP data from Sybase to text file - it will be about 14GB+ as it has images in the table.

2. Create a temp staging table on MySQL on production.

3. Load the data into the staging table on MySQL in production.

4. Rename the current MySQL production table to TableName_Backup and rename the staging table to the production table name.

I am doing the rename option because an insert/update/delete with this table is near impossible with the BLOB data that is stored with it. I did some tests on development and it was taking more than 18 hours to run an update of just a few columns - excluding the BLOB columns. When I did the rename option on development, it took seconds to execute the SQL.

Thank you for your patience in reading my post so far.

My questions are as follows: Is this a valid way to accomplish the task of re-seeding data like this? Will there be any issues with the MyISAM engine doing the rename table method?

What advice or caution can you provide?

Thank you in advance for your time and consideration.

James
↧
↧

MySQL Workbench 6.0: BETA 2 released (no replies)

July 9, 2013, 6:00 pm
$
0
0
MySQL Workbench 6.0: BETA 2 released
- http://mysqlworkbench.org/2013/07/mysql-workbench-6-0-3-beta-2-released/
- http://mysqlworkbench.org/2013/06/mysql-workbench-6-0-whats-new/
- http://mysqlworkbench.org/2013/06/mysql-workbench-6-0-home-screen/

WB 6.0 includes:
- Model (upgrade from DBDesigner)
- Query (upgrade from MySQL Query Browser)
- Admin (upgrade from MySQL Administrator)
- Migration (upgrade from MySQL Migration Toolkit)
- SSH-Tunnel

Resources:
- Downloads: http://dev.mysql.com/downloads/workbench/
- Forums: http://forums.mysql.com/index.php?151
- Blogs: http://mysqlworkbench.org/
↧

MySQL Workbench 6.0: BETA 3 released (no replies)

July 24, 2013, 5:39 pm
$
0
0
MySQL Workbench 6.0: BETA 3 released
- http://mysqlworkbench.org/2013/07/mysql-workbench-6-0-4-beta-3-released/
- http://mysqlworkbench.org/2013/06/mysql-workbench-6-0-whats-new/
- http://mysqlworkbench.org/2013/06/mysql-workbench-6-0-home-screen/

WB 6.0 includes:
- Model (upgrade from DBDesigner)
- Query (upgrade from MySQL Query Browser)
- Admin (upgrade from MySQL Administrator)
- Migration (upgrade from MySQL Migration Toolkit)
- SSH-Tunnel

Resources:
- Downloads: http://dev.mysql.com/downloads/workbench/
- Forums: http://forums.mysql.com/index.php?151
- Blogs: http://mysqlworkbench.org/
↧
Search

MySQL Workbench 6.0 is GA (no replies)

August 12, 2013, 8:57 am
$
0
0
MySQL Workbench 6.0 is GA
- https://blogs.oracle.com/MySQL/entry/mysql_workbench_6_0_new
- http://mysqlworkbench.org/2013/08/mysql-workbench-6-0-6-ga-released/
- http://mysqlworkbench.org/2013/06/mysql-workbench-6-0-whats-new/
- http://mysqlworkbench.org/2013/06/mysql-workbench-6-0-home-screen/

WB 6.0 includes:
- Model (upgrade from DBDesigner)
- Query (upgrade from MySQL Query Browser)
- Admin (upgrade from MySQL Administrator)
- Migration (upgrade from MySQL Migration Toolkit)
- SSH-Tunnel

Resources:
- Downloads: http://dev.mysql.com/downloads/workbench/
- Forums: http://forums.mysql.com/index.php?151
- Blogs: http://mysqlworkbench.org/
↧

MS ACCESS to MYSQL schemata selection empty (1 reply)

August 13, 2013, 2:21 pm
$
0
0
I am attempting to use the MYSQL Workbench Version 5.2.47 to migrate an MS Access database 2007 (file extension *.accdb) to MYSQL. The ‘Fetch Schemata List’ step completes successfully reporting no errors. Each substep (Connect to Source DBMS, Check Target DBMS Connection, and Retrieve Schema List from Source) completes successfully with a blue check mark. Here’s is the complete listing of this step:

Starting...
Connect to source DBMS...
- Connecting to source...
Connect to source DBMS done
Check target DBMS connection...
- Connecting to target...
Connecting to Mysql@localhost:3306...
Connecting to Mysql@localhost:3306...
Connected
Check target DBMS connection done
Retrieve schema list from source....
- Checking connection...
- Fetching catalog names...
- Fetching schema names...
- Fetching schema names from C:\Temp\TestDB.accdb...
- Finished
Retrieve schema list from source finished
Finished performing tasks.

However when I click next to process the ‘Schemata Selection Screen’, it is empty. All I get is the first line with the ODBC directory displayed and the second line with the following text : accdb.None. That’s it… It does not display the schema objects of the database even though it claims to have processed them successfully in the previous step.
↧
↧

SQL Server Migration fails to get schema (1 reply)

September 24, 2013, 12:48 pm
$
0
0
Greetings,
I've followed instructions for SQL Server Migration using WorkBench.
When WorkBench tries to get the schema, it fails.
If I enter the database name for Source Database, the logs end up saying "could not find catalog (my database name)"
If I leave the database name blank for Source Database, I do not get an error, but also no schema are found. It does not ask me to specify a database at all in the process.

This is on Windows (Vista) that I am running WorkBench.

Notably, I downloaded the old tool "MySQL Migration Toolkit" and that worked.
However, I'm concerned that maybe WorkBench will do a better job and I should try to get it to work instead.

Any ideas why WorkBench can't get the schema from the source database for me? While following a similar approach in the old tool works?

I've tried WorkBench 5.x and 6.x.

Thanks,
Paul
↧

migration fails when target fields renamed: "Invalid Column Name" (1 reply)

October 10, 2013, 2:03 pm
$
0
0
Hi all,

I've been pulling out my hair on this one; it SEEMS like it should work.

I'm migrating data from an old SBS2003 box running SQL Server 2005, to a new Win7 machine running MySQL Community Server (GPL) version: 5.5.24-log - Protocol version: 10.

Original DB has several table, including one named "CD_Music_Library". It included columns called "CD/TRK" and "Track#". Which are not valid column names for MySQL. I used the "Manual Editing" step to edit the "Target Object" in the "All Objects" view. I also edited the "Target Column" in the "Column Mappings" view. In both views, I renamed the target columns "CD_TRK" and "Track_Num".

All goes well, until I get to the "Bulk Data Transfer" step. Then it fails, as below:


Copy data to target RDBMS....
Migrating data...
wbcopytables.exe --odbc-source="DRIVER={SQL Server};SERVER=corp02\SQLEXPRESS;DATABASE={};UID=" --target="root@127.0.0.1:3306" --progress --passwords-from-stdin --log-level=debug3 --thread-count=2 --table-file=c:\users\xxx\appdata\local\temp\tmphuvwga
\users\xxx\appdata\local\temp\tmphuvwga

ERROR: `MusicDB`.`CD_Music_Library`:SQLExecDirect(SELECT [ARTIST], [SONG TITLE], [STYLE], [TEMPO], [TIME], [CD_TRK], [Track_Num], [COLOR CODES], [GENDER], [REF], [REG], [AutoNum], [Date] FROM [MusicDB].[dbo].[CD_Music_Library]): 42S22:1207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'CD_TRK'.
2207:[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'Track_Num'.

- `MusicDB`.`CD_Music_Library` has FAILED (0 of 16865 rows copied)


Any Ideas? from reading the logs, it sounds like the actual worker thread doesn't see the mapping. However, I don't know enough about it to know what to do next.
:(

I'm hoping that the geniuses on this board can give me a tip in the right direction!

Seems similar to [url]http://bugs.mysql.com/bug.php?id=68146[/url] but I don't have 100+ columns in the tables; only 10-20. There are 9000 rows in the table, but not many columns.

Thanks!!
↧

postgresql migration to mysql - odbc - undefined symbol (1 reply)

October 29, 2013, 2:10 pm
$
0
0
Trying to use mySQL workbench to migrate a postgresql database to mysql.

postgresql server is 8.4.13-1 on Scientific Linux 6.4

Followed the instructions from http://dev.mysql.com/doc/workbench/en/wb-migration-database-postgresql.html

Installed psqlodbc library driver, opened the workbench GUI and entered the parameters for the source posgresql database but I get the following error when I test the connection....

Could not connect to Source DBMS.
00000] [iODBC][Driver Manager]/usr/local/lib/psqlodbcw.so: undefined symbol: PQconnectdbParams (0) (SQLDriverConnect)
ODBC connection string: DRIVER=psqlodbc;SERVER=127.0.0.1;PORT=5432;DATABASE=tracsat;UID=dwills

Any ideas?
↧
Viewing all 560 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>