Home|Products|Doc|Community|Company
![]()
This document lists the VectorStar documentation available and in-development, plus links to pages, articles and other information about the technology behind our products. The classification is as follows:
· Introduction & Overviews - introductory, high-level treatment of a topic
· User & Reference Guides - user guides are user friendly, substantial treatments of a topic; reference guides are detailed and exhaustive, though spartan, lists of the whole functionality available within a system.
· Examplets, How-to's, and Tutorials - an "examplet" is a concrete example of a particular functionality in a specific context, with no further help for the reader. A "how-to" is a step by step guide on how to achieve a useful goal, along with explanatory text for the reader. A "tutorial" is a series of related, interdependent "how-to's".
·
Installation Guides - these are complete, low-level instructions
on how to install a products or an associated software on a particular platform.
For FAQs, including screenshots, a glossary,
and a bibliography,
please refer to the FAQ page.

Currently available:
· An overview of VectorStar
· An overview of xStar, VectoStar's Bulk Data Loader
· An overview of VectorStar Interface Architecture
· An overview of VectorSQL
· An overview of virtual memory and Memory Mapped Files
· An overview of vectorized operations
Soon to be available:
· An overview of Inserts, Updates, and Deletes in VectorStar
· An overview of the Fault Tolerant version of VectorStar
· An overview of columnar database technology
· An overview of data warehousing technology
· An overview of the J array programming language
· The latest version ("D") of the VectorStar/VectorSQL 2.1 BETA3.50 Commands Reference Guide
· VectorStar Future Release Schedule
· A comparison of User Defined Aggregate Functions (UDAFs) in VectorStar and Microsoft SQL Server2005
· An examplet (jpg) of the DECODE function and the AS_FOLLOWS constant "keyword" in VectorSQL
· An examplet (jpg) of the DESCRIBE_LOCALES and CURRENT_LIBRARIES functions in VectorSQL
· An examplet (jpg, txt) of the HAVING function in VectorSQL.
· An examplet of the Java Interface
VectorStar is built on top of the J Programming Language environment provided by JSoftware. A full J 6.0.2a installation is required for VectorStar to work (J systems can be installed and distributed for free). This can be achieved in several ways, click on your chosen one to obtain the corresponding J Installation Guide:
· bundled : use the standard J installation provided with VectorStar, in the VectorStar installation bundle -- this is the recommended procedure, proceed to the corresponding VectorStar Installation Guide.
· auto download : allow VectorStar to connect to the JSoftware website to download the corresponding J Installation kit -- this option requires an active internet connection.
· link : link to a preexisting J installation -- make sure that the installation is a clean, standard one that complies with VectorStar's requirements
· manual download : install J yourself -- attempt this only if you are knowledgeable in J!
·
VectorStar 2.1 x32/WIN Installation Guide
·
VectorStar 2.1 x64/WIN Installation Guide
· VectorStar 2.1 x64/LNX Installation Guide
· VectorStar 2.1 Update Guide
A C++ Compiler is needed in order to use XSTAR, our high speed loading facility used to import large amounts of data (stored as CSV files) in bulk into VectorStar.
·
Windows C++ Compiler Installation Guide
·
Linux C++ Compilter Installation Guide
Needed by the SHOW command when the FORMAT option is set to
BINARY/XLS and the VIEW_XLS option is set to EXCEL.
·
EXCEL Installation Guide
The JAVA SDK (JDK 6) is needed to use the Java VectorSQL and JDBC interfaces.
·
Java SDK Installation Guide
Needed when the GUI_LANGUAGE option is set to VB_NET.
Currently only available for the x32/WIN platform.
·
VB.NET Installation Guide
R/Rserve is needed to use VectorStar's R interface. On Windows and Linux, we have tested the interface with R-2.7.1 and it is the one we support (you should not have trouble with other versions but if you have any please contact us to sort them out).
![]()