Microsoft Technology Licensing, LLC

Kapil Gupta

James Ernest Johnson

John David Doty

Michael Ray Clark

Jonathan M Cargille

Max A Feingold

William J Carley

Christopher G Kaler

Erik B Christensen

Kenneth David Wolf

Stephen James Millet

Giovanni Moises Della-Libera

David Wortendyke

Tirunelveli R Vishwanath

Lance Olson

Richard Douglas Hill

Stefan R Batres

Umesh Madan

Michael James Coulson

Stefan Harrington Pharies

Craig Andrew Critchley

Robin Dhananjay Dhamankar

Michael Marucheck

Vijay Gajjala

Uday Sooryakant Hegde

Krishnan Srinivasan

Elliot Lee Waingold

Matthew Thomas Tavis

Tomasz Janczuk

Geary L Eppley

Stephen T Swartz

Michael Steven Vernal

David Edwin Levin

Shy Cohen

Richard Dievendorff

Dana D Groff

Douglas M Purdy

Natasha Harish Jethanandani

David Owen Driver

Siddhartha Puri

Saurab Nog

Aaron Stern

Jesus Ruiz-Scougall

Anastasios Kasiolas

Douglas A Walter

Kevin Farlee

Ryan Thomas Sturgell

Vipul A Modi

Sowmyanarayanan K Srinivasan

Scott Christopher Seely

Jonathan T Wheeler

Mohammad Makarechian

Evgeny Osovetsky

Michael J Purtell

Alexander Martin DeJarnatt

Chaitanya Dutt Upadhyay

Michael Thomas Dice

Yaniv Pessach

Erin Honeycutt

Mauro Ottaviani

Alfred M Lee, Iv

Yasser Shohoud

Eugene Shvets

Anand Rjagopalan

Mohamed-Hany Essam Ramadan

Serge Sverdlov

Vaithialingam B Balayogan

A distributed database transaction coordination manager's outcome store may be unavailable to resolve in-doubt transactions locally, e.g., after an unclean detach, during an outcomes store restore, or during a logical database restore. To facilitate transactional consistency, AGEs and values based on them are used. Some code avoids reformatting any closed physical portion for reuse based on the segment's most recently received minimum of persisted AGEs. Some code commits any in-doubt transactions that appear on an aggregate list and aborts any not on the aggregate list. Some code writes each segment's transaction commit records to persistent storage until the segment's persisted-AGE is not less than a common-restore-AGE, and some code resolves any in-doubt transactions based on a harvested outcomes list. Outcomes may reside in a log or a persisted transactions table. A restore checkpoint may include harvested outcomes. Segments may reside on cloud nodes and/or in a shared nothing database system.

Consistent database recovery across constituent segments

A transaction manager virtualization layer is provided for supporting multiple active transaction managers in a cluster or node. By virtualizing the transaction managers, applications and services are enabled to migrate across cluster nodes or even outside a cluster that includes relevant recovery mechanisms for transactions that are not completed at the time of migration. Multiple implementations of a transaction manager may be enabled to run side-by-side in a node or cluster allowing a rolling upgrade of transaction managers in clusters.

Transaction manager virtualization

The present invention extends to methods, systems, and computer program products for synchronizing ambient state among multiple transaction managers. A coordinating transaction manager establishes transaction ambient state for an application initiated transaction. The coordinating transaction manager sends and a subordinate transaction manager receives a pointer to an ambient state delegate. The subordinate transaction manager sends a request to invoke the ambient state delegate to the coordinating transaction manager in response to receiving an operation. The coordinating transaction manager invokes the ambient state delegate to format the transaction ambient state for the subordinate transaction manager. The coordinating transaction manager sends and the subordinate transaction manager receives the formatted transaction ambient state such that the subordinate transaction manager can appropriately process the operation within the scope of the transaction. The subordinate transaction manager utilizes the formatted transaction ambient state to appropriately process the operation within the scope of the transaction.

Synchronizing transaction ambient state among multiple transaction managers

Discovering transaction managers participating in a transaction. A method may be practiced, for example, in a commit tree topology including a number of transaction managers to manage transactions. The transactions include a set of operations that are all performed if a transaction is completed or all aborted if a transaction is not completed. The transaction managers store transaction result information to allow recovery of a transaction in case of system failure. The method includes receiving at a first transaction manager, a token from a second transaction manager on a machine external to the first transaction manager. The token specifies that the first transaction manager is the originator of the token. The token is associated with a transaction. The first transaction manager identifies that it has not previously participated in the transaction associated with the token. A transaction manager is identified that is participating in the transaction associated with the token.

Discovering transactions silently propagated off-machine

Minimizing transaction managers. A method that may be practiced in a commit tree topology including a plurality of transaction managers to manage transactions. The transactions include a set of operations that are all performed if a transaction is completed or all aborted if a transaction is not completed. The transaction managers store transaction result information to allow recovery of a transaction in case of system failure. The method includes acts for minimizing storage overhead by minimizing the number of transaction managers used to coordinate transactions. The method includes identifying a set of transaction managers. A first transaction manager is selected from among the set of transaction managers. A second transaction manager is identified from among the set of transaction managers that is always available when the first transaction manager is available. Messages are redirected from a subordinate associated with the first transaction manager to the second transaction manager.

Commit tree optimization based on recovery topology information

A web services namespace pertains to an infrastructure for enabling creation of a wide variety of applications. The infrastructure provides a foundation for building message-based applications of various scale and complexity. The infrastructure or framework provides APIs for basic messaging, secure messaging, reliable messaging and transacted messaging. In some embodiments, the associated APIs are factored into a hierarchy of namespaces in a manner that balances utility, usability, extensibility and versionability.

Interface infrastructure for creating and interacting with web services

Growing community of inventors

Redmond, WA, United States of America

Kapil Gupta