Microsoft Technology Licensing, LLC

60east Technologies, Inc.

David Noor

Matthew Carroll

Bekim Demiroski

Jeffrey Bernhardt

Brand Lee Hunt

Slobodan M Bojanic

Jeffrey M Birnbaum

Kaarthik Sivashanmugam

A system and method for storing and providing metadata. Metadata may be retrieved from multiple sources. The metadata is stored in facets in a repository and tagged to indicate one or more of the source, a time frame, or an associated data object. In response to receiving a request for metadata, a system selects metadata based on the specified object, source, or time frame. Access permissions corresponding to the requester are used to select and provide metadata for which the requester has permissions.

Multi-faceted metadata storage

A system and method for facilitating execution of one or more data integration projects in multiple environments or an environment that undergoes changes. Each project has a set of project parameters, which are bound to environment variables. Each environment has a corresponding environment representation with environment variables and corresponding values. Each project is mapped to an environment representation. Values of environment variables are provided to projects with corresponding parameters. When one or more projects are changed to a different environment with a different corresponding environment representation, the environment variable values of the new environment representation are provided to the projects. When an environment change is reflected in the environment representation, the changed variable values are provided to mapped projects.

Multi-environment configuration of data integration projects

The method including receiving, at a first node of a plurality of computing nodes, a message ownership migration request for a first message. The message ownership migration request can originate from a second node of the plurality of computing nodes. The first node can be an owner of the first message in a first instance of a message queue at the first node. The first message can be published from a first publisher to the message queue at one of the nodes of the plurality of computing nodes. The first message in the first instance of the message queue at the first node can be replicated at a second instance of the message queue at the second node. A first subscriber can be subscribed to the second instance of the message queue at the second node. The method also can include designating the second node as a new owner of the first message such that the first node is no longer the owner of the first message. The method further can include sending a message ownership migration notification for the first message from the first node to each of the other nodes of the plurality of computing nodes. The message ownership migration notification can identify the second node as the new owner of the first message. Other embodiments are provided.

Message queue replication with message ownership migration

Updated metadata can be requested from a set of remote servers according to a subscription registry. The subscription registry can include information for retrieving metadata from the remote servers. The requested updated metadata can be received from the remote servers. The metadata can be impact analysis and lineage metadata, and it can be requested from and received at an impact analysis and lineage metadata service. In addition, at least a portion of the metadata from the remote servers can be parsed, and a reference to a new remote server can be discovered in the metadata. Information for retrieving metadata from the new remote server can be added to the subscription registry, and metadata can be retrieved from the new remote server according to the subscription registry.

Metadata subscription registry

An execution plan for a database statement can be retrieved from a database server. References to objects can be identified in the execution plan, and metadata from the references can be assembled in a data structure on computer readable storage media. The metadata can reflect dependencies on the objects. Additionally, other dependency metadata can be augmented with the metadata from the references.

Getting dependency metadata using statement execution plans

A system and method for extracting data from an input source, transforming the data, and loading the transformed data to an output destination. A schema contract including constraints is used to validate a set of input data column types and translate them into a set of actual types. Mapping data in the schema contract enable mapping input data columns to data columns used by data integration components. The constraints and mapping data provide flexibility in transforming sets of data having different sets of input data column types, while providing a fixed set of types for use during dataflow executions. Flexibility may enable optional columns, sets of one or more columns, varying arrangements of columns, and variations in type definitions of each column.

Growing community of inventors

Redmond, WA, United States of America

David Noor