1.0
Table Of Contents
- Contents
- About the SQLFire User's Guide
- Supported Configurations and System Requirements
- Getting Started with vFabric SQLFire
- Managing Your Data in vFabric SQLFire
- Designing vFabric SQLFire Databases
- Using Server Groups to Manage Data
- Partitioning Tables
- Replicating Tables
- Estimating Memory Requirements
- Using Disk Stores to Persist Data
- Exporting and Importing Data with vFabric SQLFire
- Using Table Functions to Import Data as a SQLFire Tables
- Developing Applications with SQLFire
- Starting SQLFire Servers with the FabricServer Interface
- Developing Java Clients and Peers
- Configuring SQLFire as a JDBC Datasource
- Storing and Loading JAR Files in SQLFire
- Developing ADO.NET Client Applications
- About the ADO.NET Driver
- ADO.NET Driver Classes
- Installing and Using the ADO.NET driver
- Connecting to SQLFire with the ADO.NET Driver
- Managing Connections
- Executing SQL Commands
- Working with Result Sets
- Storing a Table
- Storing Multiple Tables
- Specifying Command Parameters with SQLFParameter
- Updating Row Data
- Adding Rows to a Table
- Managing SQLFire Transactions
- Performing Batch Updates
- Generic Coding with the SQLFire ADO.NET Driver
- Using SQLFire.NET Designer
- Understanding the Data Consistency Model
- Using Distributed Transactions in Your Applications
- Using Data-Aware Stored Procedures
- Using the Procedure Provider API
- Using the Custom Result Processor API
- Programming User-Defined Types
- Using Result Sets and Cursors
- Caching Data with vFabric SQLFire
- Deploying vFabric SQLFire
- SQLFire Deployment Models
- Steps to Plan and Configure a Deployment
- Configuring Discovery Mechanisms
- Starting and Configuring SQLFire Servers
- Configuring Multi-site (WAN) Deployments
- Configuring Authentication and Authorization
- Configuring User Authentication
- User Names in Authentication and Authorization
- Configuring User Authorization
- Configuring Network Encryption and Authentication with SSL/TLS
- Managing and Monitoring vFabric SQLFire
- Configuring and Using SQLFire Log Files
- Querying SQLFire System Tables and Indexes
- Evaluating Query Execution Plans and Query Statistics
- Overriding Optimizer Choices
- Evaluating System and Application Performance
- Using Java Management Extensions (JMX)
- Best Practices for Tuning Performance
- Detecting and Handling Network Segmentation ("Split Brain")
- vFabric SQLFire Reference
- Configuration Properties
- JDBC API
- Mapping java.sql.Types to SQL Types
- java.sql.BatchUpdateException Class
- java.sql.Connection Interface
- java.sql.DatabaseMetaData Interface
- java.sql.Driver Interface
- java.sql.DriverManager.getConnection Method
- java.sql.PreparedStatement Interface
- java.sql.ResultSet Interface
- java.sql.SavePoint Class
- java.sql.SQLException Class
- java.sql.Statement Class
- javax.sql.XADataSource
- sqlf Launcher Commands
- sqlf backup
- sqlf compact-all-disk-stores
- sqlf compact-disk-store
- sqlf encrypt-password
- sqlf install-jar
- sqlf list-missing-disk-stores
- sqlf locator
- sqlf Logging Support
- sqlf merge-logs
- sqlf remove-jar
- sqlf replace-jar
- sqlf revoke-missing-disk-store
- sqlf server
- sqlf shut-down-all
- sqlf stats
- sqlf validate-disk-store
- sqlf version
- sqlf write-data-dtd-to-file
- sqlf write-data-to-db
- sqlf write-data-to-xml
- sqlf write-schema-to-db
- sqlf write-schema-to-sql
- sqlf write-schema-to-xml
- sqlf Interactive Commands
- absolute
- after last
- async
- autocommit
- before first
- close
- commit
- connect
- connect client
- connect peer
- describe
- disconnect
- driver
- elapsedtime
- execute
- exit
- first
- get scroll insensitive cursor
- GetCurrentRowNumber
- help
- last
- LocalizedDisplay
- MaximumDisplayWidth
- next
- prepare
- previous
- protocol
- relative
- remove
- rollback
- run
- set connection
- show
- wait for
- SQLFire API
- SQL Language Reference
- Keywords and Identifiers
- SQL Statements
- SQL Clauses
- SQL Expressions
- JOIN Operations
- Built-in Functions
- Standard Built-in Functions
- Aggregates (set functions)
- ABS or ABSVAL function
- ACOS function
- ASIN function
- ATAN function
- ATAN2 function
- AVG function
- BIGINT function
- CASE expressions
- CAST function
- CEIL or CEILING function
- CHAR function
- COALESCE function
- Concatenation operator
- COS function
- COSH function
- COT function
- COUNT function
- COUNT(*) function
- CURRENT DATE function
- CURRENT_DATE function
- CURRENT ISOLATION function
- CURRENT_ROLE function
- CURRENT SCHEMA function
- CURRENT TIME function
- CURRENT_TIME function
- CURRENT TIMESTAMP function
- CURRENT_TIMESTAMP function
- CURRENT_USER function
- DATE function
- DAY function
- DEGREES function
- DOUBLE function
- EXP function
- FLOOR function
- HOUR function
- INTEGER function
- LCASE or LOWER function
- LENGTH function
- LN or LOG function
- LOG10 function
- LOCATE function
- LTRIM function
- MAX function
- MIN function
- MINUTE function
- MOD function
- MONTH function
- NULLIF expressions
- PI function
- RADIANS function
- RANDOM function
- RAND function
- RTRIM function
- SECOND function
- SESSION_USER function
- SIGN function
- SIN function
- SINH function
- SMALLINT function
- SQRT function
- SUBSTR function
- SUM function
- TAN function
- TANH function
- TIME function
- TIMESTAMP function
- TRIM function
- UCASE or UPPER function
- USER function
- VARCHAR function
- XMLEXISTS operator
- XMLPARSE operator
- XMLQUERY operator
- XMLSERIALIZE operator
- YEAR function
- SQLFire Built-in Functions
- Standard Built-in Functions
- Built-in System Procedures
- Standard Built-in Procedures
- SYSCS_UTIL.EMPTY_STATEMENT_CACHE
- SYSCS_UTIL.EXPORT_QUERY
- SYSCS_UTIL.EXPORT_TABLE
- SYSCS_UTIL.IMPORT_DATA
- SYSCS_UTIL.IMPORT_DATA_EX
- SYSCS_UTIL.IMPORT_DATA_LOBS_FROM_EXTFILE system procedure
- SYSCS_UTIL.IMPORT_TABLE
- SYSCS_UTIL.IMPORT_TABLE_EX
- SYSCS_UTIL.IMPORT_TABLE_LOBS_FROM_EXTFILE
- SYSCS_UTIL.SET_EXPLAIN_CONNECTION
- SYSCS_UTIL.SET_STATISTICS_TIMING
- JAR Installation Procedures
- Callback Configuration Procedures
- Heap Eviction Configuration Procedures
- WAN Configuration Procedures
- Standard Built-in Procedures
- Data Types
- SQL Standards Conformance
- System Tables
- ASYNCEVENTLISTENERS table
- GATEWAYRECEIVERS table
- GATEWAYSENDERS table
- MEMBERS system table
- MEMORYANALYTICS system table
- STATEMENTPLANS system table
- SYSALIASES system table
- SYSCHECKS system table
- SYSCOLPERMS system table
- SYSCOLUMNS system table
- SYSCONGLOMERATES system table
- SYSCONSTRAINTS system table
- SYSDEPENDS system table
- SYSDISKSTORES system table
- SYSFILES system table
- SYSFOREIGNKEYS system table
- SYSKEYS system table
- SYSROLES system table
- SYSROUTINEPERMS system table
- SYSSCHEMAS system table
- SYSSTATEMENTS system table
- SYSSTATISTICS system table
- SYSTABLEPERMS system table
- SYSTABLES system table
- SYSTRIGGERS system table
- SYSVIEWS system table
- Exception Messages and SQL States
- ADO.NET Driver Reference
- SQLFire Data Types in ADO.NET
- VMware.Data.SQLFire.BatchUpdateException
- VMWare.Data.SQLFire.SQLFClientConnection
- VMware.Data.SQLFire.SQLFCommand
- VMware.Data.SQLFire.SQLFCommandBuilder
- VMware.Data.SQLFire.SQLFType
- VMware.Data.SQLFire.SQLFDataAdapter
- VMware.Data.SQLFire.SQLFDataReader
- VMware.Data.SQLFire.SQLFException
- VMware.Data.SQLFire.SQLFParameter
- VMware.Data.SQLFire.SQLFParameterCollection
- VMware.Data.SQLFire.SQLFTransaction
- vFabric SQLFire Limitations
- Troubleshooting Common Problems
- vFabric SQLFire Glossary
- Index
Description
You can start servers that can host data (data stores) or those that do not host data (accessors) with the sqlf
utility, but either kind of member can service all SQL statements by routing them to appropriate data stores and
aggregating the results. Even for a member hosting data for a table, it is not necessary that all data be available
in the same member, for example, for DMLs that reference partitioned tables (PARTITION BY Clause). So
routing to other stores may be required. In addition it is possible for a member to be a data store but still not host
any data for a table due to no common SERVER GROUPS Clause.
Starting a server generates output similar to the following (XXX is the path of current working directory):
Starting SQLFire Server using multicast for peer discovery:
239.192.81.1[10334]
Starting network server for SQLFire Server at address
localhost/127.0.0.1[1527]
SQLFire Server pid: 2015 status: running
Logs generated in <XXX>/sqlfserver.log
This will start the server process locally and use the current working directory to store logs, statistics and the
data dictionary, and use multicast for peer discovery (address 239.192.81.1, port 10334). Any persistent tables
created using the default disk store will also use this directory to manage the data files.
The data dictionary is managed in a subdirectory called 'datadictionary' and persisted by default. This subdirectory
contains the persistent metadata of all the DDLs executed in the distributed system from any clients or peers,
and is necessary for a SQLFire server or locator member to start up and function properly.
As the output above indicates, a network server is also started by default that binds to localhost on port 1527.
This service allows thin clients to connect to the server and execute SQL commands using the DRDA protocol.
Always start a SQLFire server as a background process. If the server you are starting was not the last server in
the cluster to stop, it may require other cluster members to boot before it can confirm that its data is consistent
with those members' data. Even with no persistent or overflow tables, each server locally persists a copy of the
data dictionary and may have to wait for other servers to come back online to ensure that it has all the latest
updates to the data dictionary.
If another server is now started to join the cluster using the same multicast port (default port as for the first server
above), the startup message shows the other members in the distributed system:
sqlf server start -dir=server2
-client-port=1528
Starting SQLFire Server using multicast for
peer discovery: 239.192.81.1[10334]
Starting network server for SQLFire Server at
address localhost/127.0.0.1[1528]
Distributed system now has 2 members.
Other members: serv1(2015:data store)<v0>:32013/48225
SQLFire Server pid: 2032 status: running
Logs generated in <XXX>/sqlfserver.log
The italicized lines indicate the output regarding the IDs of other members in the distributed system.
The startup script maintains the running status of the server in a file .sqlfserver.ser.
Example: Multiple Servers Using Default Multicast Port for Peer Discovery
-- start a server using default mcast-port (10334) for
discovery,
-- with current directory as the working directory, and
network server
–- running on default localhost:1527
sqlf server start
–- start a second server talking to the first with dir2 as
363
sqlf Launcher Commands