Microsoft Technology Licensing, LLC

Sameet Harishanker Agarwal

F Soner Terek

Balan Sethu Raman

Jose A Blakeley

Rohan Kumar

Stefan Robert Steiner

Arkadi Brjazovski

Mahesh K Sreenivas

Istvan Cseri

Shankar Pal

Sanjay Anand

Gideon Schaller

Patrick Eugene O'Neil

Elizabeth Jean O'Neil

Nigel Clifton Westbury

Lev Novik

Paul J Leach

Wei Xiao

Richard Bruce Ward

Nigel Robin Ellis

Irena Hudis

Anil Kumar Nori

Vivek Jawahir Jhaveri

Steven John Lindell

Pedro Celis

Rajesh M Rao

Michael I Zwilling

Goetz Graefe

Surendra Verma

Michael James Zwilling

Mihai Costea

Jonathan M Cargille

Johannes Klein

Manuvir Das

Praveen Seshadri

Manuel Alfred Fahndrich

David G Campbell

Rodger N Kline

Anurag Gupta

Brian D Andrew

Michael Eric Deem

J Patrick Thompson

Soner Terek

Ganapathy Subramaniam Krishnamoorthy

Kangrong Yan

Hannes Helmut Ruescher

Sambavi Muthukrishnan

Jeffrey A East

William Hunter Hudson

Ramanathan N Venkatapathy

Spencer Wong Low

Jacob Lacouture

Dale Woodford

Lewis S Bruck

Arthur T Whitten

Prasanna V Krishnan

William Hiroaki Shihara

Daniel W Weise

Rande Blackman

Albert L Lingelbach

Craig G Zastera

Gary Gilchrist

An operating system is provided. The system includes an agent component to monitor computer activities between one or more single-item access components and one or more set-based access components. A protocol component is employed by the agent component to mitigate data access between the single-item access components and the set-based access components.

Multi-protocol access to files and directories

The present invention relates to a system and methodology to facilitate security for data items residing within (or associated with) a hierarchical database or storage structure. A database security system is provided having a hierarchical data structure associated with one or more data items. The system includes a security component that applies a security policy to the data items from a global location or region associated with a database. Various components and processes are employed to enable explicit and/or inherited security properties to be received by and propagated to the data items depending on the type of data structure encountered or processed.

System and methods providing enhanced security model

A file namespace hierarchy bypass and method to access files are provided. The bypass can be employed, for example, as a computer-readable medium with instructions for generating a unique identifier associated with a file and instructions for accessing the file based on the unique identifier and a specified search space. A computer-readable medium having instructions for obtaining the unique identifier and specified search space associated with the file and instructions for generating a path designation by combining the unique identifier and the specified search space used to access the file may also be employed. The method for bypassing the namespace hierarchy of the file, for example, may include passing the unique identifier and specified search space to a program and accessing the file based on a path designation generated by the program by combining the unique identifier and specified search space.

Bypass of the namespace hierarchy to open files

Data management between a common data store and multiple applications of multiple disparate application frameworks. A data storage component is provided that facilitates the storage of data, which data includes structured, semi-structured, and unstructured data. A common data platform interfaces to the data storage component to provide data services accessible by a plurality of disparate application frameworks, which data services allow a corresponding application of the different frameworks to access the data.

Platform for data services across disparate application frameworks

An operating system is provided. The system includes an agent component to monitor computer activities between one or more single-item access components and one or more set-based access components. A protocol component is employed by the agent component to mitigate data access conflicts between the single-item access components and the set-based access components.

Systems and methodologies for integration of an anti virus AV Plug In(s) as part of an Item Store. The semantics for operation of the AV Plug In(s) are provided by the relational Item Store, via employing a metadata component and a scanning component associated with the Item Store. The metadata component can supply a signature value being associated with the Item Store that can represent the time of scanning of data, and outcome for every scanned item. The scanning component can provide for a queuing of items in the data store in a synchronous and/or asynchronous mode for both scanning and cleaning by the AV Plug In supplied by vendors.

Anti virus for an item store

A system and method for synchronizing a database comprising raw data and metadata derived from the raw data, but when the metadata has not yet been updated. The raw data and the metadata are first synchronized, with the raw data having been assigned a version number. After synchronization, any stale metadata will be updated and assigned the same version number as the raw data.

Synchronization with derived metadata

An XML based type-definition language for declaring content-index for WinFS Types is provided. Content-index declarations can be specified for the Item type as well as it's sub-entities like Fragments, etc across Item type hierarchies. The properties of WinFS types in the schema are marked for content-indexing by the schema designer. Installing the content-index definitions includes parsing content-index definitions in the schema, generation of appropriate SQL statements for data extraction and storing the SQL statements.

Type definition language for defining content-index from a rich structured WinFS data type

Techniques and tools for implementing a source code annotation language are described. In one aspect, keywords are added to a function interface to define a contract for the function independent of function call context. In another aspect, annotations are inserted at global variables, formal parameters, return values, or user-defined types. The annotations include, for example, properties and qualifiers. A property can indicate, for example, a characteristic of a buffer. In another aspect, an annotation indicates that a value has usability properties sufficient to allow a function to rely on the value, where the usability properties depend on value type.

Source code annotation language

A technique for representing the structure of hierarchically-organized data in a non-hierarchical data structure, such as a relation. The hierarchically-organized data is represented as a tree, and each node in the tree is assigned a position identifier that represents both the depth level of the node within the hierarchy, and its ancestor/descendant relationship to other nodes. The data represented by each node, as well as its position identifier, is stored in a row of a relational database, thereby capturing the hierarchical structure of the data in such relational database. A technique is provided for the compressed storage of position identifiers in a format that allows an efficient bytewise comparison of position identifiers to determine relative order and ancestry.

System and method for relational representation of hierarchical data

A file stream exchange system and method are provided. The system can be employed, for example, with a storage system that supports transactions as a primary mechanism and employs a rich type system. The system provides a mechanism for the storage system to provide reliable updates to file streams while preserving the common criteria for security. The system includes a replace stream component which is a kernel mode mechanism that allows transactional exchange of stream data of two file-backed items without violating the common criteria for security.

Mechanism to exchange primary data stream of a file

Various embodiments of the present invention are directed to systems and methods for synchronizing mixed elements (MEs) comprising structure data and unstructured filestreams between peer computer systems in a hardware/software interface system environment that does not permit snapshotting of large unstructured ME filestreams during synchronization. For several such embodiments, the method comprises synchronizing the ME in two steps, one for snapshotting the structured data component of the ME (as well as the cv of the filestream but not the filestream itself) and one for locking and transmitting the filestream to the receiving sync peer if and only if, after being locked, it is determined that the filestream is unchanged from the time of the ME data component snapshot.

Systems and methods for synchronization of items without snapshots

Various embodiments of the present invention are directed to a data store comprising Items, Elements, and Relationships. An Item is a unit of data storable in a data store and further comprises said Element and said Relationship. An Element is an instance of a type comprising one or more fields. A Relationship is a link between at least two Items. The data store further comprising a Core Schema to define a set of Core Items by which a hardware/software interface system understands and directly processes said set of Core Items in a predetermined and predictable way. The Core Items are derived (directly or indirectly) from a common single Base Item which, in turn, is a foundational Item in a Base Schema.

Systems and methods for data modeling in an item-based storage platform

A database view of a database is created which provides a transaction-consistent view of an existing database at a previous time. Each database view contains all the information needed to, along with the primary database, determine the contents of the primary database at a previous time. The database view consists of a side file corresponding to each data file in the primary database. The side files contain a copy of all data from the corresponding data file which has been changed since the database view was created. Sparse files may be used for the side files in order to conserve space. Page table data is kept in order to allow a quick determination as to whether the page from the primary database has been modified and the old version stored in the database view side file.

Transaction consistent copy-on-write database

Growing community of inventors

Redmond, WA, United States of America

Sameet Harishanker Agarwal