Rules and guidelines for MySQL sources and targets
Rules and guidelines for MySQL sources
and targets
Use the following rules and guidelines for MySQL sources
and targets
:
The database user account for each target connection must have the INSERT, SELECT, UPDATE, and DELETE privileges.
You cannot include lookup fields of Text or Ntext data type because MySQL connections use a UTF-8 code page.
When you use a saved query to read data from a MySQL source, you must not use the full outer join operation.
When you use a saved query to read data from a MySQL source that contains Float columns, the Secure Agent imports the Float data type as Real data type.
When you use a saved query to read data from a MySQL source that contains Double columns, the Secure Agent imports the Double data type as Decimal data type.
You cannot use the
select * from <table_name>
command in a saved query. You must provide the explicit column list.
When you read time data from a MySQL source, the
synchronization
task converts the time to the Coordinated Universal Time (UTC) time zone. Consider the time zone change if you create data filters and field mapping expressions based on time.
If a task writes time data from a MySQL source to a flat file, the
synchronization
task converts the time data to a Date/Time data type. The date is the current date and time is the time specified in the source. You can use a string function in an expression to remove the date before loading data to the flat file.
When you configure partitioning in a mapping to read data from MySQL, do not define a partition for the Date column. If the configured partition is for a Date column, the mapping fails because of a third-party issue.
When you run a synchronization task to write data to a MySQL target, the Secure Agent writes one record with o value to the target even if the primary key column of the target is not connected to any source port.
When you run a mapping task to create a target, the target is successfully created at runtime. If you drop the created target table and run the task again, the task fails.
When you run a MySQL mapping to read from a stored procedure, ensure that the precision of the Float data type does not exceed 18.
Consider the following rules and guidelines when you add objects with a hyphen in the column names in the Source and Target transformations:
When the source column name that you read has hyphens and you use the
Create New at Runtime
option to create a target, the hyphens in the table name are converted to underscores in the target column.
If you add a new column to the object in an existing mapping and the column name has a hyphen, you cannot manually add these columns in the mapping.
If you parameterize the target object, the manual field map option in the
Field Mapping
tab is not applicable. You must select Automatic, Completely Parameterized, or Partially Parameterized as the field map options for the mapping to work successfully.