DAVID IMRAN NOOR
Pilots at 170 Ave, Redmond, WA
License number
Washington A5052401
Issued Date
Feb 2012
Expiration Date
Feb 2017
Category
Airmen
Type
Authorized Aircraft Instructor
Address
Address
7912 170Th Ave NE UNIT 305, Redmond, WA 98052
Professional information
David Noor
Location:
Greater Seattle Area
Industry:
Computer Software
Work:
Microsoft Corporation
- Redmond, WA Jun 2010 - Jan 2012
-
Principal Development Manager
Microsoft, SQL Server
Mar 2007 - Jun 2010
-
Senior Dev Lead
IBM Entity Analytic Solutions
Jan 2005 - Mar 2007
-
Manager, Performance and Scalability Engineering
Systems Research and Development
Jun 2003 - Dec 2004
-
Member of Technical Staff
Pixio Corp
Oct 2002 - Apr 2003
-
Software Architect
Rogue Wave Software
May 1996 - Oct 2002
-
Software Architect
Education:
Northwest University 2012 - 2014
Master of Arts, Counseling Psychology Oregon State University 1991 - 1996
BS, Computer Science
Master of Arts, Counseling Psychology Oregon State University 1991 - 1996
BS, Computer Science
Skills:
SQL Server, Cloud Computing, Distributed Systems, Architecture, Software Design, C++, SSIS, Data Quality, Identity Resolution, C#, ETL, Data Integration, Multithreading, Grid Computing, Visual Studio, Rogue Wave, Python, Systems Engineering, OData, Web Services, Windows Azure, SQL Azure, Sqoop, Hadoop, DB2, SQL, Microsoft SQL Server
Multi-Environment Configuration Of Data Integration Projects
US Patent:
2011030, Dec 15, 2011
Filed:
Jun 15, 2010
Appl. No.:
12/816378
Inventors:
Bekim Demiroski - Shanghai, CN
David Noor - Redmond WA, US
Jeffrey Bernhardt - Woodinville WA, US
Matthew Carroll - Seattle WA, US
David Noor - Redmond WA, US
Jeffrey Bernhardt - Woodinville WA, US
Matthew Carroll - Seattle WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 9/44
US Classification:
717124
Abstract:
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-Faceted Metadata Storage
US Patent:
2011030, Dec 15, 2011
Filed:
Jun 11, 2010
Appl. No.:
12/813523
Inventors:
David Noor - Redmond WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 17/30
US Classification:
707746, 707E17143
Abstract:
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.
Metadata Subscription Registry
US Patent:
2011025, Oct 13, 2011
Filed:
Apr 8, 2010
Appl. No.:
12/756196
Inventors:
David I. Noor - Redmond WA, US
Slobodan M. Bojanic - Redmond WA, US
Slobodan M. Bojanic - Redmond WA, US
Assignee:
MICROSOFT CORPORATION - Redmond WA
International Classification:
G06F 15/16
US Classification:
709203, 709217
Abstract:
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.
Getting Dependency Metadata Using Statement Execution Plans
US Patent:
2011028, Nov 17, 2011
Filed:
May 12, 2010
Appl. No.:
12/778128
Inventors:
Kaarthik Sivashanmugam - Bellevue WA, US
David I. Noor - Redmond WA, US
David I. Noor - Redmond WA, US
Assignee:
MICROSOFT CORPORATION - Redmond WA
International Classification:
G06F 17/30
US Classification:
707705, 707E17001
Abstract:
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.
Schema Contracts For Data Integration
US Patent:
2011029, Dec 1, 2011
Filed:
May 27, 2010
Appl. No.:
12/788310
Inventors:
Matthew Carroll - Seattle WA, US
David Noor - Redmond WA, US
David Noor - Redmond WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 17/30
US Classification:
707756, 707802, 707769, 707E17044, 707E17014
Abstract:
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.