VSys One: Volunteer Management Software

Databases

VSys One can be configured to connect to any number of different databases at startup, or just one. Database connection information is stored in the VSys.ini file, and that file is often shared among multiple users if they access a common VSys.exe file. VSys can use either NexusDB version 1, (1.07+), NexusDB version 3, or SQL Server 2008 or higher.

The tools here let you tell VSys One where the data is stored and how to access it. With the exception of NexusDB standalone data they do not create these databases: you must do that in your database application first. See each database's details for those requirements.

VSys works hard to make the DBA's life easy - it:

• Makes its own tables and indices, no scripts are needed. When VSys is first connected to a database, it will check for its required tables and prompt you to create any tables and indices not present.
• Can work on multiple databases at once (production, testing, training) with no special magic. Set up any number of database connections, and VSys will prompt you, when it starts up, for which database to use.
• Does its own schema updates. If VSys starts up and sees that a column is missing or too narrow, tables need to be created or indices added, it will offer to make the changes automatically and nondestructively.
• Makes its own backups when prompted, and does so in a database-independent manner (a backup made on SQL Server can be restored SQL Server or NexusDB, and vice-versa).

VSys One works with SQL Server 2008 or 2008R2, 2012, or for small installations, NexusDB. Server load is relatively small and VSys One does not require its own SQL Server instance or hardware, just its own database within an existing instance. It has no preference as to whether this database is running on its own physical hardware or in a virtual environment.

Disk space utilized depends entirely on your data.