1.1.1

1. System properties
If a system property named sqlfire.<property-name> is defined and its value is not an empty string,
then its value will be used for the named configuration attribute.
2. Connection properties
Properties can be passed in a Properties object passed to the DriverManager.getConnection method.
3. File properties
Otherwise, if a property is defined in a Specifying a Property File on page 230 found by this application, and
its value is not an empty string, then its value will be used for that attribute.
4. Defaults
Otherwise a default value is used.
Specifying a Property File
When running the interactive sqlf tool, you can specify the location of the properties file using the -p
propertyfile option on the command line when you start sqlf.
The name of a property file can be optionally specified using the sqlfire.properties system property.
If the system property is set to an absolute file name then that file is used as the property file. If the system
property is set to a relative file name then it is searched for in the below locations. If the system property is not
set, then the name of the property file defaults to sqlfire.properties and is searched for in the following
locations:
1. Current directory (directory in which the process was launched)
2. User's home directory
3. Class path (loaded as a system resource)
Persisting the Data Dictionary
By default, SQLFire persists the data dictionary for any data store member (members that use the host-data=true
boot property). When persistence is enabled for a SQLFire member, the member preserves all table, index,
trigger, and procedure definitions in a disk store, even when all members of the distributed system are down.
When the system is brought back up, there is no need to re-execute the data definition statements (DDL).
Persistence of the data dictionary is controlled by the persist-dd boot property. By default, this property is set
to true for all members that host data. You must specify a consistent persist-dd value for all data stores in the
same SQLFire cluster. You cannot enable persistence for SQLFire accessors in a cluster.
The data dictionary is always replicated and available on each peer member of the distributed system. So, even
if data dictionary persistence is turned off, the dictionary is preserved as long as there is at least one member of
the distributed system running. If all members are brought down when persistence is turned off, you must
re-execute the DDL to restore your database.
The persistent data is written to a disk store the directory specified by the connection property sys-disk-dir .
Each member must specify its own unique directory. When a member is brought up, it looks to other members
for data before reading its persistent files. That is, live data overrides persistent data.
Optimizing Availability and Performance on page 87 provides more informationa bout starting and shutting
down SQLFire clusters that utilize disk stores for persistence.
vFabric SQLFire User's Guide230
Deploying vFabric SQLFire