Microsoft Technology Licensing, LLC

David W Olix

Chadwin James Mumford

Balendran Mugundan

Peter Gvozdjak

Raghu Ram

Jimmy Yu Wu

Matthew Alban Neerincx

Zlatko Michailov

Junfeng Dong

Sapna Daryanomal Jeswani

Rohan Samuel Lam

Matt A Neerincx

Aspects of the subject matter described herein relate to database access. In aspects, a request for access to a database is received at a node of a database cluster. Also received at the node is an intent associated with the request. If the intent is to potentially write to the database, a primary instance of the database services the request. If the intent is to read from but not write to the database, an identifier of a secondary instance of the database is sent to the requestor for use in accessing the database.

Discovery and client routing to database nodes

Aspects of the subject matter described herein relate to database connectivity behavior. In aspects, an entity seeking to access data that is replicated via instances of a database follows a plan. The plan provides information as to which instance(s) the entity is to attempt to access the data from. The plan may include connection data that indicates parameters the entity is to use in connecting to the instance(s). The plan may also indicate one or more other instances from which the entity may attempt to access the data if the client is not able to access the data from initial instance(s).

Modeling distribution and failover database connectivity behavior

A first computer establishes a logical connection to a second computer for requesting and/or receiving data from a database. A logical connection is independent of the underlying physical network connection used to connect to the database. A context identifier is stored by both computers to enable the context of a logical connection to be persisted between switches from one physical network connection to another within the logical connection thus enabling database transfers to be continued on a second physical network connection when a failure in a first physical network connection occurs.

Transparent database connection reconnect

Aspects of the subject matter described herein relate to buffering database server response data. In aspects, a database driver receives a request for data from a requester such as an application. Based on the request and information associated with a query, the database driver determines whether the requester is allowed to obtain data that has been previously buffered. If the database driver determines that the requester is not allowed to obtain data that has been previously buffered, the database driver indicates that blocks corresponding to the data may be freed. The database driver obtains new blocks from the database when they are needed. The database driver may determine whether to free blocks depending on a mode in which the blocks are accessed. When blocks are requested in a stream mode, they may be discarded once provided to a requester unless a bookmark has been set.

Adaptive buffering of database server response data

Growing community of inventors

Woodinville, WA, United States of America

David W Olix