A database table in a SQL map contains a column with the data type of timestamp. This column is returned as part of the result set. The map editor can not accomidate this data type therefore it is moving the data for the next column into the 'timestamp' field within the map.

Since the field in the map with the corresponding timestamp data type cannot be populated the data read into that field is going to the next field in the map causing all subsequent fields to be incorrect.

No error message - the data getting inserted into database is off a column.

From Microsoft's site:
Despite the name a SQL Server timestamp column is not based on the system time and does not contain a date or time value. Instead the timestamp column is an array of binary values.

Since it is an array of binary values it can not be pulled into the map as a field which causes all of the column numbers after it to be off.

Either edit the view or query so that it does not have a timestamp in the result set.