File based and highly available hybrid database
May 23, 2012. Estimated Expiration Date is calculated based on simple USPTO term provisions. It does not account for terminal disclaimers, term adjustments, failure to pay maintenance fees, or other factors which might affect the term of a patent.Patent ReferencesCommunication for version management in a distributed information service Method and apparatus for automatic loading of a data set in a node of a communication network File backup system Reliable database administration arrangement Method for balancing of distributed tree file structures in parallel computing systems to enable recovery after a failure Method and system for variable authority level user access control in a distributed data processing system having multiple resource manager System for providing user access control within a distributed data processing system having multiple resource managers Method and apparatus for reducing response time in automated library data retrieval systems Object transferring system and method in an object based computer operating system Point of sale system having backup file device Patent #: 5313664 InventorsAssigneeApplicationNo. 884816 filed on 05/18/1992US Classes:707/8, Concurrency (e.g., lock management in shared database)707/9, Privileged access707/201, Coherency (e.g., same view to multiple users)710/200ACCESS LOCKINGExaminersPrimary: Black, Thomas G.Assistant: Homere, Jean R. Attorney, Agent or FirmInternational ClassesG06F 017/00G06F 012/00 AbstractA file based and highly available hybrid database using resident databases (16, 17, 18) on data control computer systems (31, 32, 33) which are linked together as part of a computer network (29). Resident databases (16, 17, 18) are selected to store master file groups (19,21,22,23) the information being copied to other resident databases (16, 17, 18). All database transactions are controlled by interacting client (11) and server (12, 13, 14) processes using the computer network (29) to copy a master file group (19, 21, 22, 23) to the client system for use and then restores the master file group (19, 21, 22, 23) to the appropriate master database (16, 17, 18). | |
