Data type mapping   The data types of columns must map correctly between your consolidated and remote database. For details, see Microsoft SQL Server data mapping.

CHAR columns   In Microsoft SQL Server, CHAR data types are fixed length and blank-padded to the full length of the string. In MobiLink remote databases (SQL Anywhere or UltraLite) CHAR is the same as VARCHAR: values are not blank-padded to a fixed width. It is recommended that you use VARCHAR in the consolidated database rather than CHAR. If you must use CHAR, the mlsrv12 -b command line option can be used to remove trailing blanks from strings during synchronization. This option is important for string comparisons used to detect conflicts.

See -b mlsrv12 option.

SET NOCOUNT ON   For Microsoft SQL Server, you should specify SET NOCOUNT ON as the first statement in all stored procedures or SQL batches executed via ODBC.

Procedure calls   Microsoft SQL Server requires that procedure calls with parameters be written using the ODBC syntax:

{ CALL procedure_name( {ml param1}, {ml param2}, ... ) }

Sample database uses computer columns   The SQL Server AdventureWorks sample database contains computed columns. You cannot upload to a computed column. You can set the column to be download-only, or you can exclude the column from synchronization.

Implementing conflict detection in an upload_update script   The behavior of the SQL Server NOCOUNT option means that the MobiLink server cannot accurately assess how many rows were changed by an upload data script. For SQL Server, you must perform conflict detection directly in the upload_update script by passing in both the old and the new row values. See upload_update table event.