VistaDB 6
VistaDB / How does VistaDB work? / Data Engine and SQL Query Processor
In This Topic
    Data Engine and SQL Query Processor
    In This Topic

    VistaDB provides developers with a rich set of data management features for building robust, world-class .NET database applications.

    Transaction processing

    VistaDB implements a state-of-the art transaction processing (TP) architecture. The foundation of VistaDB's TP architecture is called versioned or serializable transactions, which is based on Snapshot isolation level transactions. This isolation eliminates the need for VistaDB to lock tables, rows or database pages when involved in a transaction. There is no concept of "row locking " when in a transaction using ReadCommitted Isolation, which minimizes lock escalation and thereby reduces the deadlock problems for read patterns.

    Each VistaDB transaction receives its own snapshot view of the database when the transaction starts. While in the transaction, modifications are isolated from all other transactions (transactions started by other processes) until the transaction has been committed to the database or has been rolled back. Rollbacks are in fact effortless and never jeopardize the integrity of a database, nor do they cause lock problems.

    Small Footprint

    VistaDB maintains the incredibly small footprint of less than 1 MB. Our small engine size allows your .NET applications to be deployed easily. Furthermore, the VistaDB engine does not require any special registration on the client machines. All licenses are handled at compile time integration with Visual Studio. Using the Microsoft ILMerge utility you can fully embed our Assembly in your EXE for even greater integration.

    Full Referential Integrity

    VistaDB manages cascading deletes and updates within the relationships defined, thereby providing full referential integrity. VistaDB actually handles a number of cascading scenarios that SQL Server cannot handle.

    Row and Table-Level Locking

    VistaDB provides full support for concurrency through row-level and table-level locking.

    See Also