Abstract: An apparatus enabling a user to perform a simulated bicycling exercise includes a frame, two mounting points defining an axis, the two mounting points comprising an upper rear mounting point comprising an upper rear rotating joint and a lower front mounting point comprising a pivoting connection arrangement proximate to and interacting with the frame, the pivoting connection arrangement comprising at least one resistive element configured to provide resistive force returning the frame to a neutral centered orientation from an off-centered orientation and pedals associated with a wheel and the frame, the pedals enabling the user, when facing forward, to apply force to the pedals and rotate the wheel. The frame is configured to receive forces from the user and dissipate the forces into frame leaning forces such that the user has an ability to cause the frame to pivot about the two mounting points by leaning to one side.

Abstract: Various shaped abrasive particles are disclosed. Each shaped abrasive particle includes a body having at least one major surface and a side surface extending from the major surface.

Abstract: A device includes: a first portion configured to be grasped by the hand of the user, and a second portion defining a reservoir containing a control material, wherein the control material contains a target analyte in a known or predetermined concentration. A method of verifying the accuracy of an analyte monitoring device includes receiving a fluid sample, identifying the fluid sample as a control solution, and analyzing the fluid sample.

Abstract: Virtual databases are provisioned using point-in-time copies of a source database. Transaction logs received from the source database are applied to a point-in-time copy of the source database to create recovery milestones comprising database blocks that can be used to provision virtual databases. The recovery milestones are created in advance of receiving a request to provision a virtual database. Each recovery milestone is validated to determine that a consistent database snapshot can be created using the recovery milestone. If a problem is identified that prevents creation of a consistent database snapshot, the problem is fixed before creating the next recovery milestone. In response to receiving a request to provision a virtual database corresponding to a point in time, a recovery milestone is identified and transaction logs applied to the recovery milestone to create a database snapshot corresponding to the requested point in time.

Abstract: Techniques are provided to allow users to define a global service that is offered across multiple replicated databases. Database clients connect to and use a global service just as they do with regular services on a single database today. Upon receiving a connection request, a collection of components, referred to collectively as the Global Data Service framework (GDS framework), automatically chooses the best database server instances to which to connect a client. Once those connections have been established, the clients determine which database server instance, of those database server instances to which they are connected, to send requests to based, at least in part, on advisory messages sent to the clients by the GDS framework.

Abstract: Techniques are provided to allow users to define a global service that is offered across multiple replicated databases. Database clients connect to and use a global service just as they do with regular services on a single database today. Upon receiving a connection request, a collection of components, referred to collectively as the Global Data Service framework (GDS framework), automatically chooses the best database server instances to which to connect a client. Once those connections have been established, the clients determine which database server instance, of those database server instances to which they are connected, to send requests to based, at least in part, on advisory messages sent to the clients by the GDS framework.

Abstract: Techniques are provided to allow users to define a global service that is offered across multiple replicated databases. Database clients connect to and use a global service just as they do with regular services on a single database today. Upon receiving a connection request, a collection of components, referred to collectively as the Global Data Service framework (GDS framework), automatically chooses the best database server instances to which to connect a client. Once those connections have been established, the clients determine which database server instance, of those database server instances to which they are connected, to send requests to based, at least in part, on advisory messages sent to the clients by the GDS framework.

Abstract: Virtual databases are provisioned using point-in-time copies of a source database. Transaction logs received from the source database are applied to a point-in-time copy of the source database to create recovery milestones comprising database blocks that can be used to provision virtual databases. The recovery milestones are created in advance of receiving a request to provision a virtual database. Each recovery milestone is validated to determine that a consistent database snapshot can be created using the recovery milestone. If a problem is identified that prevents creation of a consistent database snapshot, the problem is fixed before creating the next recovery milestone. In response to receiving a request to provision a virtual database corresponding to a point in time, a recovery milestone is identified and transaction logs applied to the recovery milestone to create a database snapshot corresponding to the requested point in time.

Abstract: Virtual databases are provisioned using point-in-time copies of a source database. Transaction logs received from the source database are applied to a point-in-time copy of the source database to create recovery milestones comprising database blocks that can be used to provision virtual databases. The recovery milestones are created in advance of receiving a request to provision a virtual database. Each recovery milestone is validated to determine that a consistent database snapshot can be created using the recovery milestone. If a problem is identified that prevents creation of a consistent database snapshot, the problem is fixed before creating the next recovery milestone. In response to receiving a request to provision a virtual database corresponding to a point in time, a recovery milestone is identified and transaction logs applied to the recovery milestone to create a database snapshot corresponding to the requested point in time.

Abstract: Virtual databases are provisioned using point-in-time copies of a source database. Transaction logs received from the source database are applied to a point-in-time copy of the source database to create recovery milestones comprising database blocks that can be used to provision virtual databases. The recovery milestones are created in advance of receiving a request to provision a virtual database. Each recovery milestone is validated to determine that a consistent database snapshot can be created using the recovery milestone. If a problem is identified that prevents creation of a consistent database snapshot, the problem is fixed before creating the next recovery milestone. In response to receiving a request to provision a virtual database corresponding to a point in time, a recovery milestone is identified and transaction logs applied to the recovery milestone to create a database snapshot corresponding to the requested point in time.

Abstract: Techniques are provided to allow users to define a global service that is offered across multiple replicated databases. Database clients connect to and use a global service just as they do with regular services on a single database today. Upon receiving a connection request, a collection of components, referred to collectively as the Global Data Service framework (GDS framework), automatically chooses the best database server instances to which to connect a client. Once those connections have been established, the clients determine which database server instance, of those database server instances to which they are connected, to send requests to based, at least in part, on advisory messages sent to the clients by the GDS framework.

Abstract: An aircraft display and control system generally includes a processor, a cursor control and selection device, a multifunction keyboard, an aeronautical information database, a geographic database, and a plurality of display devices. Users, such as an aircraft pilot and copilot, can perform flight plan entry and modification by manipulating graphical and textual information on the display devices using the cursor control device and the multifunction keyboard. In one embodiment, the present invention provides an interface to flight deck information systems that is intuitive and easy to use, and which enables flight crew members to easily and effectively enter and modify data displayed by the aircraft flight deck, substantially centralizes avionics controls within one controller, and decreases flight crew “heads-down” time.

Abstract: Techniques are described herein for returning a repository to a prior state. The repository may be, for example a database, and the prior state may be, for example the consistent state that the database had at a particular point in time in the past. When a operator-caused error has been introduced to the database by changes made by an already-committed transaction, the techniques described herein may be used to recover from the error by returning the database to a point in time prior to the commit time of the transaction that introduced the error. The techniques involve the generation of “physical undo” information, and the use of the physical undo information in conjunction with physiological undo and physiological redo to efficiently return a repository to the prior state.

Abstract: According to an example embodiment, a method for changing the display of a function on a flight deck display having a plurality of non-overlapping display regions comprises the steps of, receiving a first input that identifies the function, receiving a second input that identifies a first display region of the plurality of non-overlapping display regions, and displaying at least a portion of the first function using the first display region in response to receiving the first input and receiving the second input.

Abstract: Techniques are described herein for returning a repository to a prior state. The repository may be, for example a database, and the prior state may be, for example the consistent state that the database had at a particular point in time in the past. When a operator-caused error has been introduced to the database by changes made by an already-committed transaction, the techniques described herein may be used to recover from the error by returning the database to a point in time prior to the commit time of the transaction that introduced the error. The techniques involve the generation of “physical undo” information, and the use of the physical undo information in conjunction with physiological undo and physiological redo to efficiently return a repository to the prior state.

Abstract: An aircraft display and control system generally includes a processor, a cursor control and selection device, a multifunction keyboard, an aeronautical information database, a geographic database, and a plurality of display devices. Users, such as an aircraft pilot and copilot, can perform flight plan entry and modification by manipulating graphical and textual information on the display devices using the cursor control device and the multifunction keyboard. In one embodiment, the present invention provides an interface to flight deck information systems that is intuitive and easy to use, and which enables flight crew members to easily and effectively enter and modify data displayed by the aircraft flight deck, substantially centralizes avionics controls within one controller, and decreases flight crew “heads-down” time.

Abstract: Techniques are described herein for returning a repository to a prior state. The repository may be, for example a database, and the prior state may be, for example the consistent state that the database had at a particular point in time in the past. When a operator-caused error has been introduced to the database by changes made by an already-committed transaction, the techniques described herein may be used to recover from the error by returning the database to a point in time prior to the commit time of the transaction that introduced the error. The techniques involve the generation of “physical undo” information, and the use of the physical undo information in conjunction with physiological undo and physiological redo to efficiently return a repository to the prior state.

Abstract: A high performance speedboat with a planing type hull and incorporating a drive mechanism having a one or two-speed-forward, step-up, V-gear, hydraulic transmission, which connects the engine drive shaft and the propeller shaft in V-drive structure. The propeller shaft extends rearwardly through the boat transom to provide a "thru-drive" system in coaction with a unitary strut and stern steering support assembly for placement on the boat transom. Such assembly includes a planar transom member secured to the boat transom, and a rearwardly extending, generally horizontal, planar structural member secured to the transom member and extending rearwardly of the boat. The structural member is bifurcated and has a pair of spaced rear end portions having rudder support means operatively disposed thereon for receiving rudder assemblies therein. Also provided is a pair of spaced strut support members secured to the assembly and extending downwardly therefrom with each having a propeller shaft support.