VistaDB 5
Gibraltar VistaDB > How does VistaDB work? > VistaDB Zero Config
VistaDB Zero Config

VistaDB does not have to be "installed" before it is used on a target machine. There are no services to be installed that often require elevated privileges (often called Serverless design). You don't even need to create an administrator to build or assign permissions to the database. There are no required configuration files for the database to be deployed.

Shared Hosting - nothing to install

We designed VistaDB to handle the shared hosting environment as well. Most users do not have permissions to install anything on their shared host. Many .NET components are not Medium Trust compliant and often require the admin on the machine to put them in the GAC or give them special permissions. Not so with VistaDB. Put the runtime DLL in your bin folder and FTP the site.

The VistaDB embedded database engine processes SQL commands and performs low-level reading and writing of data in VistaDB databases. The entire VistaDB engine is contained in a single less than 1 MB fully managed assembly which may be freely deployed with your applications. The engine (i.e. assembly) does not require any special registration or configuration on the end-user machine. It can be placed in the same directory as your applications or it can be installed to the GAC. Another way to deploy the VistaDB is to fully embed it into your EXE using Microsoft ILMerge. We call this ZeroClick deployment since there is no additional files or assemblies to deploy with your application.

Windows Elevated Rights (User Access Control)

VistaDB requires no elevated rights on Windows (UAC) in order to run.  It can even run with a low-privilege (guest) user account.  This is a notable contract to the requirements of SQL Express and other server engines.

Isolated Storage

VistaDB even supports running from Isolated Storage for increased control if you are running Active Directory. Isolated Storage files are moved with users roaming profiles and are controlled in size and permissions through Active Directory.

See Also