Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
faq:migration-toolkit:fk-convert [2019/07/19 12:40] darya.prikhodkina |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== How to Ensure that Foreign Key is Converted Successfully from MySQL to Microsoft SQL Server ====== | ||
| - | |||
| - | Foreign keys in MySQL and in MSSQL has the same structure. | ||
| - | Structure of the Foreign key in MSSQL: | ||
| - | [ FOREIGN KEY ] | ||
| - | REFERENCES [ schema_name . ] referenced_table_name [ ( ref_column ) ] | ||
| - | [ ON DELETE { NO ACTION | CASCADE | SET NULL | SET DEFAULT } ] | ||
| - | [ ON UPDATE { NO ACTION | CASCADE | SET NULL | SET DEFAULT } ] | ||
| - | |||
| - | Structure of the Foreign key in MySQL: | ||
| - | FOREIGN KEY [id] (index_col_name, ...) | ||
| - | REFERENCES tbl_name (index_col_name, ...) | ||
| - | [ON DELETE {RESTRICT | CASCADE | SET NULL | NO ACTION}] | ||
| - | [ON UPDATE {RESTRICT | CASCADE | SET NULL | NO ACTION}] | ||
| - | |||
| - | The only difference is RESTRICT word in MySQL, that has no equivalent in MSSQL database. | ||
| - | But in MySQL foreign key constraints are checked immediately, so NO ACTION and RESTRICT are the same. | ||
| - | During import no errors should arise. To check if conversion of the actions of Foreign keys was successful, please check the database. | ||
| - | |||
| - | |||
| - | \\ | ||
| - | ---- | ||
| - | === More about Ispirer Systems === | ||
| - | [[https://www.ispirer.com|Ispirer Home Page]] | ||
| - | [[https://www.ispirer.com/products/database-migration|Database Migration]] | ||
| - | [[https://www.ispirer.com/application-conversion|Application Conversion]] | ||
| - | [[https://www.ispirer.com/download|Downloads]] | ||