Member Avatar for kool.net

hi,
can any one tell me how to i use my sql sever's databse itno ms sql 2008 server.
I tried to to do dat with the help of mysql backup file & execute it on ms sql server, but there are some syntax related problems.
please help me.
thanks in advance

  • 3 Contributors
  • 2 Replies
  • 120 Views
  • 9 Hours Discussion Span
  • Latest Post Latest Post by sknake

Dani AI

Generated

tried to execute a MySQL dump directly in SQL Server, which is why you hit syntax errors: a MySQL export contains MySQL-only DDL (backticks, ENGINE=..., AUTO_INCREMENT, ENUM, zero-date values, etc.) that SQL Server does not understand. That explains the failures rather than a broken backup.

Two practical paths (build on points from and ):

  • Use a migration tool that converts schema and data (less manual editing). Microsoft’s SQL Server Migration Assistant for MySQL is built for this and shows data-type mappings and conversion reports: .
  • For simple data-only moves or ad-hoc transfers, create an ODBC connection to MySQL (MySQL Connector/ODBC) and use SQL Server’s Import/Export Wizard or SSIS. That copies rows quickly but leaves you to fix schema, indexes and constraints: Import/Export Wizard and Connector/ODBC.

Quick checklist and common gotchas to handle after conversion:

  • Map AUTO_INCREMENT to SQL Server IDENTITY(1,1).
  • Convert TEXT/LONGTEXT to VARCHAR(MAX)/NVARCHAR(MAX) as needed.
  • TINYINT(1) often represents booleans in MySQL — confirm before mapping to BIT.
  • ENUM/SET need a VARCHAR plus constraints or a lookup table.
  • Handle MySQL zero-dates ('0000-00-00') before migrating; SQL Server rejects them.
  • Re-write stored procedures, triggers and MySQL-specific SQL (e.g., LIMIT) manually.

Suggested workflow:

  1. Backup both systems. 2) Run schema conversion (SSMA) and review mappings. 3) Migrate data (ODBC or SSMA). 4) Recreate indexes, FKs and constraints by hand for performance. 5) Run row-count and query tests, then adapt application SQL/connection strings. Test thoroughly in a dev environment before switching production.

Recommended Answers

All 2 Replies

Member Avatar for baki100

migrating from one rdbms to another is not as simple as dumping the sql scripts in the new rmdbs, unless you convert the entire script by hand a simpler solution is use a migrator tool to migrate and old dbms to a new one.

Edited by baki100 because: n/a
Member Avatar for sknake

You DTS or the Import/Export data wizard on SQL Server 2008 to copy the data. You should be able to set up an ODBC data source to connect to your MySQL database then let SQL Server handle the rest.

The table structures will be rough and unindexed so you should create a new set of tables by hand with proper indexes, relationships, datatypes, etc. After that just insert the data in to the newly created tables.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.