1.1.1

Table Of Contents
DescriptionOption
Congures the working directory for any other SQL command les
executed from within the script. The -path entry is prepended to
-path
any SQL script le name executed that the script executes in a run
command.
If the servers or locators have been congured to use authentication,
this option species the user name to use for booting the server and
joining the distributed system.
-user
Description
Specify one of these pairs of options with the command to connect to a SQLFire Distributed system and execute
a SQL command le:
Use both -client-bind-address and -client-port to connect to a SQLFire cluster as a thin client
and perform the command.
Use both mcast-port and -mcast-address, or use the -locators property to connect to a SQLFire
cluster as a peer client and perform the command.
The -file argument species the location of the SQL script le to execute. If the script le itself calls other
script les using run 'filename', also consider using the -path option to specify the location of the
embedded script les. If an exception occurs while executing the script, SQLF immediately stops executing
script commands, unless you include the -ignore-errors option.
Examples
This command connects to a SQLFire network server running on myserver:1234 and executes commands in the
ToursDB_schema.sql le:
sqlf run -file=c:\sqlfire\quickstart\ToursDB_schema.sql
-client-bind-address=myserver -client-port=1234
This command executes the loadTables.sql script, which calls dependent scripts such as
loadCOUNTRIES.sql, loadCITIES.sql, and so forth. If you execute this command outside of the directory
in which the dependent scripts are located, you must specify the working directory using the -path option. For
example:
sqlf run -file=c:\sqlfire\quickstart\loadTables.sql
-path=c:\sqlfire\quickstart
-client-bind-address=myserver -client-port=1234
sqlf server
A SQLFire server is the main server side component in a SQLFire system that provides connectivity to other
servers, peers, and clients in the cluster. It can host data. A server is started using the server utility of the sqlf
launcher.
Syntax on page 391
Description on page 396
Example: Multiple Servers Using Default Multicast Port for Peer Discovery on page 398
Example: Servers and Client Using Locator on page 398
Example: Multiple Locators for High Availability on page 399
Example: Servers and Accessors with a Locator on page 399
Example: Servers and Locator Using BUILTIN Authentication on page 400
Example: Servers and Accessors with Server Groups and Locator on page 401
391
sqlf Launcher Commands