Depending on its length. MySQL Server 5.6 and higher can have CHAR columns with a length up to 255 characters. Anything larger is migrated as LONGTEXT.
NCHAR
CHAR/LONGTEXT
Depending on its length. MySQL Server 5.6 and higher can have VARCHAR columns with a length up to 65535 characters. Anything larger is migrated to one of the TEXT blob types. In MySQL, a character set of strings depends on the column character set instead of the data type.
VARCHAR
VARCHAR/MEDIUMTEXT/LONGTEXT
Depending on its length. MySQL Server 5.6 and higher can have VARCHAR columns with a length up to 65535 characters. Anything larger is migrated to one of the TEXT blob types.
NVARCHAR
VARCHAR/MEDIUMTEXT/LONGTEXT
Depending on its length. MySQL Server 5.6 and higher can have VARCHAR columns with a length up to 65535 characters. Anything larger is migrated to one of the TEXT blob types. In MySQL, a character set of strings depends on the column character set instead of the data type.
DATE
DATE
DATETIME
DATETIME
DATETIME2
DATETIME
Date range in MySQL is '1000-01-01 00:00:00.000000' to '9999-12-31 23:59:59.999999'. Note: fractional second values are only stored as of MySQL Server 5.6.4 and higher.
SMALLDATETIME
DATETIME
DATETIMEOFFSET
DATETIME
TIME
TIME
TIMESTAMP
TIMESTAMP
ROWVERSION
TIMESTAMP
BINARY
BINARY/MEDIUMBLOB/LONGBLOB
Depending on its length.
VARBINARY
VARBINARY/MEDIUMBLOB/LONGBLOB
Depending on its length.
TEXT
VARCHAR/MEDIUMTEXT/LONGTEXT
Depending on its length.
NTEXT
VARCHAR/MEDIUMTEXT/LONGTEXT
Depending on its length.
IMAGE
TINYBLOB/MEDIUMBLOB/LONGBLOB
Depending on its length.
SQL_VARIANT
not migrated
There is not specific support for this data type.
TABLE
not migrated
There is not specific support for this data type.
HIERARCHYID
not migrated
There is not specific support for this data type.
UNIQUEIDENTIFIER
VARCHAR(64)
A unique flag set in MySQL. There is not specific support for inserting unique identifier values.
SYSNAME
VARCHAR(160)
XML
TEXT
2.语法和功能差异
SQL Server 和 GreatSQL 在语法、数据类型、函数、存储过程等方面存在一定的差异。某些在 SQL Server 中使用的语法和功能可能在 GreatSQL 中不支持，或者需要进行修改和调整。
$ /opt/mssql-tools/bin/sqlcmd -S localhost -U SA -P'xxx'
复制
2.创建测试数据
3> CREATEDATABASE test2024; 4> go 5> use test2024 6> go Changeddatabasecontextto'test2024'. 1> CREATETABLE t1 (idint,namevarchar(30)) 2> go 1> 2> INSERTINTO t1 values (1,'a'),(2,'b'),(3,'c') 3> go
(3rows affected) 1> SELECT * from t1 2> go idname ----------- ------------------------------ 1 a 2 b 3 c
(3rows affected)
复制
六、配置数据迁移
1.启动迁移功能
双击打开MySQL workbench，点击数据迁移功能，再点击开始迁移按钮
2.配置源端/目标端
2.1 源端选择 Microsoft SQL Server
需要安装SQL Server驱动：Download Microsoft® SQL Server® 2012 Native Client - QFE from Official Microsoft Download Center https://www.microsoft.com/zh-cn/download/details.aspx?id=50402
Online copy of table data to target RDBMS:此方法（默认）将数据复制到目标端数据库。
Create a batch file to copy the data at another time:数据也可以转储到一个稍后可以执行的文件中，或者用作备份。此脚本使用MySQL连接来传输数据。
Create a shell script to use native server dump and load abilities for fast migration:与执行实时在线复制的简单批处理文件不同，这会生成一个要在源主机上执行的脚本，然后生成一个Zip文件，其中包含在目标主机上本地迁移数据所需的所有数据和信息。复制并提取目标主机上生成的Zip文件，然后执行导入脚本（在目标主机上），使用LOAD data命令将数据导入MySQL。
13.批量数传输
根据上一步所选的选项，进行数据传输
14.迁移报告
数据迁移完成后，会自动生成报告，总结了整个迁移过程
七、目标端 GreatSQL 查询数据
登录 GreatSQL 查询数据
greatsql> SHOWDATABASES; +--------------------+ | Database | +--------------------+ | adm | | das | | information_schema | | mysql | | performance_schema | | sys | | sys_audit | | test2024 | +--------------------+ 8 rows in set (0.00 sec)
greatsql> SELECT * FROM test2024.t1; +------+------+ | id | name | +------+------+ | 1 | a | | 2 | b | | 3 | c | +------+------+ 3 rows in set (0.00 sec)
复制
总结
MySQL workbench 支持从某些特定 RDBMS 产品迁移到 GreatSQL（MySQL），更多功能的使用可以前往 MySQL 官网进行查看。
