5. Connecting to the Installation : Connecting to a Remote Server
Share this page                  
Connecting to a Remote Server
Remote access to an Actian server requires a hostname, an instance ID, a connection protocol, and a username and password.
This information can be predefined in a Server Connection Definition (also known as a virtual node (vnode) in the Connectivity Guide), or can be specified dynamically in the connection string (known as a dynamic vnode).
Dynamic Vnode
The dynamic form is the typical way to connect to a remote server in Vector.
To specify this information dynamically in the connection string, use the format:
For example, to use the Terminal Monitor to connect to the pocdb database of instance VH on host host1, use either of the following examples:
sql @host1,tcp_ip,VH;[actian,actian]::pocdb
sql +user=actian @host1,tcp_ip,VH:pocdb
Static Vnode
For frequently used remote targets, the hostname, instance ID, connection protocol, and username and password can be included in a single Server Connection Definition, known as a static (or predefined) vnode. Then, the vnode name can be used to reference the entire connection string.
For example, the following command will start a Terminal Monitor (sql) session to the database pocdb on the instance defined by the vnode myvnode:
sql myvnode::pocdb
You can define static vnodes using the Actian Network Utility on Windows or the netutil command on Linux.