Thursday, November 17, 2005
Firebird Novice's Guide
Firebird Novice's Guide: "Distributed Database - Application Flexibility
When you need to move your desktop database to something more sophisticated or enlarge a small workgroup application so that several departments can use it, InterBase is ideal. It was designed for distributed database environments.
Multi-Database Access
InterBase is a truly distributed SQL database server that lets each database system query and return information to any other InterBase server.
Automatic Two-Phase Commit
Multi-database transactions require more than just the ability to connect to two databases. To be transactions, they must be consistent and atomic. InterBase includes a two-phase commit that ensures that distributed updates are consistent, automatically.
Distributed Two-Phase Commit Recovery
InterBase goes beyond a simple two-phase commit. It was the first database to provide distributed recovery from a failure during a two-phase commit. This ensures full recovery with no single point of failure, since the co-ordination of the commit is distributed among all the servers. A transaction that cannot commit across all servers, is automatically rolled back on all servers."
When you need to move your desktop database to something more sophisticated or enlarge a small workgroup application so that several departments can use it, InterBase is ideal. It was designed for distributed database environments.
Multi-Database Access
InterBase is a truly distributed SQL database server that lets each database system query and return information to any other InterBase server.
Automatic Two-Phase Commit
Multi-database transactions require more than just the ability to connect to two databases. To be transactions, they must be consistent and atomic. InterBase includes a two-phase commit that ensures that distributed updates are consistent, automatically.
Distributed Two-Phase Commit Recovery
InterBase goes beyond a simple two-phase commit. It was the first database to provide distributed recovery from a failure during a two-phase commit. This ensures full recovery with no single point of failure, since the co-ordination of the commit is distributed among all the servers. A transaction that cannot commit across all servers, is automatically rolled back on all servers."
# posted by Dr. Martin Menzel @ 6:48 AM 
