Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
faq:migration-toolkit:manage-errors [2019/06/12 18:37]
127.0.0.1 external edit
faq:migration-toolkit:manage-errors [2019/07/25 10:37]
darya.prikhodkina
Line 1: Line 1:
-====== How does SQLWays ​manage errors ​======+====== How Does SQLWays ​Manage Errors ​======
  
   * There are three types of errors that might occur during the migration:​\\ \\   * There are three types of errors that might occur during the migration:​\\ \\
-    - **Export error** – when our tool cannot recognize ​some part of the source code. In this case the error is raised on the export and depicted in the //​**sqlways.log**//​ file after the migration.\\ \\ +    - **Export error** – when the tool cannot recognize ​any part of the source code. In this case the error is raised on the export and depicted in the //​**sqlways.log**//​ file after the migration.\\ \\ 
-    - **Import error** – when our tool made the conversion incorrectly or it doesn’t correspond to the syntax supported in the database. In this case the error is raised on the import and depicted in the //​**sqlways_imp.log**//​ after the migration.\\ \\ +    - **Import error** – when the tool performed ​the conversion incorrectly or it doesn’t correspond to the syntax supported in the database. In this case the error is raised on the import and depicted in the //​**sqlways_imp.log**//​ after the migration.\\ \\ 
-    - **BL (Business ​Logics) error** – sometimes the target (result) syntax is correct, but it works incorrectly. The object is created but returns ​another ​result different from the result that returns ​the source SQL Code or simply returns ​the error. BL error is the most difficult to find error as it raised only when you check the work of the target database manually or through the application using the converted database.+    - **BL (Business ​Logic) error** – sometimes the target (result) syntax is correct, but it works incorrectly. The object is createdbut returns ​the result different from the one which is returned by the source SQL Code or it simply returns ​an error. BL error is the most difficult to find error as it raised only when you check the work of the target database manually or through the application using the converted database.
  
 \\ \\