Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 11.0.1 (Français) » SQL Anywhere Server - SQL Reference » Using SQL » SQL statements » SQL statements (A-D)



Use this statement in a SQL Anywhere remote database to create a MobiLink user.

[ TYPE network-protocol ]
[ ADDRESS protocol-options ]
[ OPTION option=value, ... ]
ml_username: identifier
network-protocol : 
| http 
| https 
| tls
protocol-options : string
value: string | integer
  • ml_username   A name identifying a MobiLink user.

    For more information about MobiLink users, see Introduction to MobiLink users.

  • TYPE clause   This clause specifies the network protocol to use for synchronization. The default protocol is tcpip.

    For more information about communication protocols, see CommunicationType (ctp) extended option.

  • ADDRESS clause   This clause specifies protocol-options in the form keyword=value, separated by semi-colons. Which settings you supply depends on the communication protocol you are using (TCPIP, TLS, HTTP, or HTTPS).

    For a complete list of protocol options, see MobiLink client network protocol option summary.

  • OPTION clause   The OPTION clause allows you to set extended options using option=value in a comma-separated list.

    The values for each option cannot contain equal signs or semicolons. The database server accepts any option that you enter without checking for its validity. Therefore, if you misspell an option or enter an invalid value, no error message appears until you run the dbmlsync command to perform synchronization.

    Options set for a synchronization user can be overridden in individual subscriptions or on the dbmlsync command line.

    For information about extended options, see MobiLink SQL Anywhere client extended options.

    The network-protocol, protocol-options, and options can be set in several places.

    For information about how dbmlsync processes options that are specified in different locations, see Priority order.

    This statement causes options and other information to be stored in the SQL Anywhere ISYSSYNC system table. Anyone with DBA authority for the database can view the information, which could include passwords and encryption certificates. To avoid this potential security issue, you can specify the information on the dbmlsync command line.

    See dbmlsync syntax.


Must have DBA authority.

Side effects

Automatic commit.

See also
Standards and compatibility
  • SQL/2003   Vendor extension.


The following example creates a MobiLink user named SSinger, who synchronizes over TCP/IP with a server computer named using the password Sam. The use of a password in the user definition is not secure.

TYPE http
OPTION MobiLinkPwd='Sam';