This verb can be executed either locally on the producer station of the Sql connection or from any client station of the producer. In the latter case, commands and returned data are routed transparently through the multi-station messaging system. Multiple connections to the same data source are only allowed if using different Sql Connections. Multiple connections using the same Sql Connection will be refused, however, multiple simultaneous requests using the same Sql Connection is possible.

A connection, and the data associated to it, are managed in the context of user sessions. A connection should only be handled in the context of the session that had originally initiated it; and all related objects must be properly released/closed before the session is ended. For example, it is not possible to initiate a connection at start up and have requests executed in any user context.

This mode is asynchronous. The program must monitor the value of the status variable.

Similar to the state of communication objects, these modes are designed to prevent a Sql connection's producer station to execute actual commands towards the Data Source by giving the application designer the ability to set Sql connections in a state (stopped) in which actual commands are not processed. The modes START and STOP are always executed locally (as opposed to routed to the station producing the Sql connection). As a consequence, they must be executed on producer stations of the Sql connection to be truly effective - as opposed to being executed on stations issuing requests that are routed to the Sql connection producer over the multi-station network.