The Data Virtuality Server is currently available in three versions: 2.1, 2.3, and 2.4. We recommend checking carefully that you are reading the right documentation for your version.
The documentation for each version consists of five parts: Administration Guide, User Guide, Reference Guide, Upgrade Guide, and Licensing and Copyright.
Administration Guide is aimed mostly at administrators and provides information on how to install the Data Virtuality Server and other software, configure it, and keep it running smoothly. It also includes an Upgrade Guide describing how to upgrade the Data Virtuality Server to a later version.
User Guide describes how replication and materialization work in the Data Virtuality Server, how to set up query builders, and so on. In other words, it gives some theoretical information to help you with working with the Data Virtuality Server.
Reference Guide gives technical information on the SQL dialect, procedures, commands, schemas, and other elements used in the Data Virtuality Server. This guide is more a handbook, although it is supplied with examples; you can find more practical examples in the Zendesk HelpCenter which contains articles often written on the basis of real user cases.
Upgrade Guide provides a step-by-step manual on how to upgrade your Data Virtuality Server.
Licensing and Copyright contains the license for the use of trial software, list of third-party open source components used for development of each component of the software, and third-party licenses.
Tips and Tricks
Before you proceed to reading the Data Virtuality Server documentation, you might want to read this section: it contains some practical information to help you to get the most out of it.
How to read and use additional information
Some information in the guide is specially formatted to make it easier for you to single out important information or pick something useful. There are four types of such information: Info, Tip, Note, and Warning, and here are descriptions of each of them:
Just additional information: for example, that the feature is implemented starting from a particular version.
Tips, tricks, and hints: for instance, if a process is too time-consuming when there is too much data, we may suggest a way to make it more efficient.
Important information and remarks - such as names of properties being case sensitive.
Critically important information - for example, we will include a special warning if the particular procedure deletes all information without further confirmation.
How to copy code from snippets
All snippet boxes come with a Copy button in the top right corner. Clicking it will copy all the code in the snippet (line numbers not included).
How to search using wildcards
At the moment, due to platform limitations, wildcards cannot be used at the beginning of a search keyword, but there is a workaround for this: just format your search keywords as a regular expression. For example, if you need to search for
?hum*, you can type
/.*hum.*/. The search will the return occurrences of words including 'hum', such as hum, human, and inhumane.