Considerations for SQL Mapping
Note: If you use the SQL syntax on both sides of a map,
each side must use a separate set of data sources. One side cannot
refer to the data sources belonging to the other side of the map.
For outbound processing, you need a way to determine which records in the database tables were processed. Therefore, you must be able to mark records so that when you process the map, you can select only the unprocessed records in the tables.
To mark records as processed or not processed, you must designate a column in your database to contain a processing flag. This can be a process column that you insert into your database, or an unused column. You must incorporate this column into the SQL statement record in your map. Also, you must update this column from the map to indicate that a data record was processed.
Note: Before adding a process column to your database
or changing the function of an existing column, copy your data to
separate work tables in your database. Copying your data ensures that
your testing will not overwrite existing data.
The Sterling B2B Integrator Map Editor enables you to export data directly to a database.
Note: When you copy and paste map components on the
SQL side of a map, any links from the copied SQL structure are not
preserved.