Skip to content

conversion-settings-mysqltosql.md

Latest commit

 

History

History
74 lines (47 loc) · 2.31 KB

conversion-settings-mysqltosql.md

File metadata and controls

74 lines (47 loc) · 2.31 KB
title Conversion Settings (MySQLToSQL)
description Conversion Settings (MySQLToSQL)
author nilabjaball
ms.author niball
ms.date 01/19/2017
ms.service sql
ms.subservice ssma
ms.topic concept-article
ms.collection
sql-migration-content
f1_keywords
ssma.mysql.preferencesdetailcontrol.f1

Conversion Settings (MySQLToSQL)

The 'Settings' tab allows the user to set node level settings. The tab will be available at the following Metabase nodes:

  • Database Node

  • Functions Category

  • Function Node

  • Tables Category

  • Table Node

Specifications:

The Settings tab has two user settings, viz.:

  1. Function Conversion

  2. Table Conversion

These settings will be available based on the type of Metabase node. For example, Function Conversion related setting will not be available at the Table Node

Note

  • The changes made by the user will be saved in the Project Workspace as a separate preference file.
  • The extension of this file will be ccprefs.

  1. Function Conversion Setting:

    1. This tab contains 'Force function conversion' option. The option can have one of the following four values:

      • Convert according to project settings [inherited]

      • Always Convert to a Function

      • Always Convert to a Procedure

      • Convert according to project settings

    2. Based on the settings, the function will be converted either to a function or to a stored procedure.

    3. The settings made by the user are saved in the cascaded preferences file on clicking Apply button.

  2. Table Conversion Setting:

    1. This tab contains 'Suppress ROWID auxiliary column generation' option. The option can have one of the following four values:

      • Convert according to project settings [inherited]

      • Yes

      • No

      • Convert according to project settings

    2. If 'Yes', this setting prohibits creation of ROWID auxiliary column creation on target tables.

    3. The settings made by the user are saved in cascaded preferences file on clicking Apply button.

See Also

Project Settings (Conversion) (MySQL to SQL)