Microsoft Technology Licensing, LLC

Samer Boshra

Dharma Kiritkumar Shukla

Karthik Raman

Momin Mahmoud Al-Ghosien

Shireesh Kumar Thota

Madhan Gajendran

Pankaj Sharma

Ankur Savailal Shah

Hari Sudan Sundar

Liang Li

Krishnan Sundaram

Mikhail Mikhailovich Koltachev

Adrian Ilcu Predescu

Brandon Chong

Aravind Ramachandran Krishna

Karan Vishwanath Popali

Praveen Seshadri

Scott A Konersmann

Sameer Arun Verkhedkar

Atul Katiyar

Shawn Bice

Matt Hollingsworth

Rajeev Sudhakar Bhopi

Jayanta Mondal

Oliver Drew Leonard Towers

Siddhesh Dilip Vethe

Vinod Sridharan

Maciej Sarnowicz

Charlie D Carson

Ken Van Hyning

Omri Bahat

Robert Hutchinson

Orestis Kostakis

Balachandar Perumalswamy

Vivek Ravindran

Ashwini Singh

Emily Lawton

Artavazd Ginosian

Lalitha Manjapara Viswanathan

Edward W Dudenhoefer

Data sets such as databases are often distributed over a number of servers, where each server stores a subset of records and an index that enables the server to locate the records in response to queries. However, tight coupling of indexing and storage may limit load-balancing, fault recovery, and distribution. Instead, the set of servers may be partitioned into a set of storage servers that store the records and a set of index servers of the index over the records. In a set that is decoupled in this manner, load-balancing may involve provisioning and locating index servers independently of the provisioning and locating of the storage servers in view of the particular sensitivities and tolerances of various applications. Additionally, the index servers may also utilize a data layout that is selected and adapted independent of the data layout of the storage servers and/or the schema of the data stored thereby.

Schema-agnostic indexing of distributed databases

Databases are often provided according to various organizational models (e.g., document-oriented storage, key/value stores, and relational database), and are accessed through various access models (e.g., SQL, XPath, and schemaless queries). As data is shared across sources and applications, the dependency of a data service upon a particular organizational and/or access models may become confining. Instead, data services may store data in a base representation format, such as an atom-record-sequence model. New data received in a native item format may be converted into the base representation format for storage, and converted into a requested format to fulfill data requests. Queries may be translated from a native query format into a base query format that is applicable to the base representation format of the data set, e.g., via translation into an query intermediate language (such as JavaScript) and compilation into opcodes that are executed by a virtual machine within the database engine.

Unified data organization for multi-model distributed databases

Workloads are often performed by a server set according to a service level agreement, and are often provisioned and load-balanced by dedicating selected computational resources (e.g., servers and bandwidth) for application to the workload. However, resource-based provisioning may not accurately reflect the computational resource expenditure of the workload, leading to overprovisioning or underprovisioning of servers for the workload. Instead, the workload may be evaluated according to a service unit as a measurement of a volume of computational resources consumed by a workload unit, including performance dimensions specified in the service level agreement. The service level agreement may indicate a service unit rate for the workload. The workload may therefore be allocated to a subset of servers in portions according to a service unit rate, where the sum of the service unit rates for the portions allocated to the servers satisfies the service unit rate specified in the service level agreement.

Data service provisioning, metering, and load-balancing via service units

Embodiments are directed to implementing a dynamically changeable system model that is customizable per version, programmatically generating system models at runtime and to extending a programmatically generated system model. In an embodiment, a computer system determines that a dynamically changeable system model corresponds to a managed system. The dynamically changeable system model includes various managed system objects. The computer system indicates for the dynamically changeable system model which managed system objects are available in each version of the managed system. The available managed system objects are stored in a data store of the dynamically changeable system model. The computer system requests the managed system to provide current managed system information including at least a version identifier and, based on the managed system information indicated by the managed system, provides to the dynamically changeable system model those managed system objects that are provided by the indicated version of the managed system.

Model slicing and versioning

Data-tier application components (DACs) and methods for managing database applications are disclosed. According to one particular embodiment, a DAC includes a single unit of management that packages metadata related to a database object. The metadata related to the database object includes an identifier of the database object, a database runtime resource identifier of a database runtime resource operable to manipulate the database object, and a policy related to execution of the database runtime resource.

Data-tier application component

Growing community of inventors

Woodinville, WA, United States of America

Samer Boshra