We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byMaximilian Horner
Modified about 1 year ago
Inaport Training Standard Matching
© Copyright 2010 InaPlex Inc Matching Process of deciding which record or set of records in the target table(s) should be updated Alternatively, decide if record already exists and take appropriate action
© Copyright 2010 InaPlex Inc Matching Techniques Inaport supports different ways to match Standard build expressions on source and target Fuzzy Refine Standard to allow for bad data SQL Use SQL SELECT instead of expressions
© Copyright 2010 InaPlex Inc Standard Matching Easiest, most flexible of the techniques Can match on ANY field or combination of fields Can apply expressions for incoming and/or target records independently Source: normcomp(#MyCompany) Target: normcomp((#Account) Use AND / OR to provide complicated matches
© Copyright 2010 InaPlex Inc How it Works For each table with Standard matching Read the match fields Build an in memory index for each table The target match expression is applied to the field data read from the table As each record comes in The source match expression is applied to the record The resulting value is found in the in memory index If necessary, in memory index is updated after changes are applied to database
© Copyright 2010 InaPlex Inc Matching Example Company Match on name, phone area code Person Match on first & last name Import leads to Company - Person
© Copyright 2010 InaPlex Inc Select Match Type On the Operation Tab, select “Standard Matching”
© Copyright 2010 InaPlex Inc Company Relationships Only need primary key as this is top table
© Copyright 2010 InaPlex Inc Company Match Tab Build expressions on source side and target side E.g. name and phone number area code Using normcomp() function to normalise company name. This will lower case, equalise spaces, remove noise words Remember – results will be compared exactly
© Copyright 2010 InaPlex Inc Company Map Tab Need to make sure all fields used in matching are mapped when creating records In memory indexes will be updated
© Copyright 2007 InaPlex Limited Matching – Parent/Child Two parts Table relationships Specify primary/foreign keys using data dictionary, expression editor Primary key from parent used to find related records in child Match expressions Further refine matches on tables AFTER relationships have been used
© Copyright 2010 InaPlex Inc Person Relationships As the Person table is a child of Company, need to specify the foreign key that relates child table to parent Inaport will normally fill in automatically
© Copyright 2010 InaPlex Inc Person Match tab Matching on first and last name E.g. Concatenate names, then normalise
© Copyright 2010 InaPlex Inc Person Map Tab As with Company, it is important to ensure that match fields are also mapped, or indexes may not be updated correctly
© Copyright 2010 InaPlex Inc Benefits Easy to understand Works across all target systems Very flexible matching Can use any combination of fields Can use simple or complex expressions for either source or target Can do “OR” matching – specify multiple different match criteria, match on any High speed for moderate data sets 200,000 – 400,000 records
© Copyright 2010 InaPlex Inc Drawbacks Can be slow for large (>400,000) data sets Up front cost of building indexes –Inaport has to read data from target and build the index Memory cost of indexes –Large indexes can consume a lot of memory Ultimately, is an exact match criteria Can use expressions such as norm() Consider Fuzzy Matching if issue
© Copyright 2010 InaPlex Inc Summary Standard Matching is powerful, flexible and easy to understand For dirty data, consider Fuzzy Matching For large data sets, consider SQL Matching Remember You can mix and match – use different match techniques on different tables
© Copyright 2007 InaPlex Limited THANK YOU
Inaport Training Introduction to Matching. Matching The purpose of Inaport is to: Extract data from a source Transform that data Load into a target Loading.
Inaport Training Fuzzy Matching. © Copyright 2010 InaPlex Inc Matching Process of deciding which record or set of records in the target table(s) should.
Methodology - Logical Database Design. 2 Step 2 Build and Validate Local Logical Data Model To build a local logical data model from a local conceptual.
Microsoft ® Access ® 2010 Training Create Queries for a New Database If a yellow security bar appears at the top of the screen in PowerPoint, click Enable.
Microsoft ® Office Access ® 2007 Training Build a database IV: Create queries for a new Access database ICT Staff Development presents:
De-normalize if… Performance is unsatisfactory Table has a low update rate –(sacrifice flexibility) Table has a high query rate –(speed up retrieval)
Microsoft ® Access ® 2010 Training Create queries for a new database.
1 Access Lesson 3 Creating Queries Microsoft Office 2010 Introductory.
Copyright 2007, Paradigm Publishing Inc. ACCESS 2007 Chapter 2 BACKNEXTEND 2-1 LINKS TO OBJECTIVES Creating Related Tables Creating Related Tables Determining.
Build a database IV: Create queries for a new Access database Overview: Ask your data — create queries It’s time to create queries, one of the most powerful.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
SQL IMPLEMENTATION & ADMINISTRATION Indexing & Views.
Microsoft Office 2013: In Practice Chapter 2 Using Design View, Data Validation, and Relationships Copyright © 2014 by The McGraw-Hill Companies, Inc.
Introduction to Databases Angela Clark University of South Alabama.
1Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall. Exploring Microsoft Office Access 2010 by Robert Grauer, Keith Mast, and Mary Anne.
1 Chapter 17 Methodology - Local Logical Database Design.
Views Lesson 7. Skills Matrix View A view can be queried just like a table. Microsoft describes a view as either a virtual table or a stored SELECT query,
Chapter 6 Methodology Logical Database Design for the Relational Model Transparencies © Pearson Education Limited 1995, 2005.
1 Access Lesson 3 Creating Queries Microsoft Office 2010 Introductory Pasewark & Pasewark.
Switch off your Mobiles Phones or Change Profile to Silent Mode.
Copyright © 2005 Ed Lance Fundamentals of Relational Database Design By Ed Lance.
Ultimate Bundle Overview Products Benefits Technical Requirements Licensing Pricing Valid until 01-Sep-2010.
ASP.NET Programming with C# and SQL Server First Edition Chapter 7 Working with Databases and SQL Server Express.
1 Database Systems: A Practical Approach to Design, Implementation and Management International Computer Science S. Carolyn Begg, Thomas Connolly Lecture.
® Microsoft Access 2010 Tutorial 9 Using Action Queries and Advanced Table Relationships.
CSCI 3140 Module 3 – Logical Database Design for the Relational Model Theodore Chiasson Dalhousie University.
Agenda 2/20/13 o Review quiz, answer questions o Review database design exercises from 2/13 o Create relationships through “Lookup tables” o Discuss.
Database Planning Database Design Normalization.
Tutorial 9 Using Action Queries and Advanced Table Relationships.
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 1 1. Chapter 2: Relational Databases and Multi-Table Queries Exploring Microsoft Office.
© 2008 The McGraw-Hill Companies, Inc. All rights reserved. ACCESS 2007 M I C R O S O F T ® THE PROFESSIONAL APPROACH S E R I E S Lesson 9 – Building Links,
Database Systems, 8 th Edition SQL Performance Tuning Evaluated from client perspective –Most current relational DBMSs perform automatic query optimization.
A table is a set of data elements (values) that is organized using a model of vertical columns (which are identified by their name) and horizontal rows.
Databases Week 7 LBSC 690 Information Technology.
Logical Database Design Nazife Dimililer. II - Logical Database Design Two stages –Building and validating local logical model –Building and validating.
Microsoft Office 2007 Access Chapter 3 Maintaining a Database.
CSC271 Database Systems Lecture # 30. Summary: Previous Lecture Normalization summary/example Remaining steps/activities in building logical data.
Fundamentals, Design, and Implementation, 9/e Chapter 5 Database Design.
Database Design Concepts INFO1408 Term 2 week 1 Data validation and Referential integrity.
Week 11 Creating Framed Layouts Objectives Understand the benefits and drawbacks of frames Understand and use frame syntax Customize frame characteristics.
Description and exemplification use of a Data Dictionary. A data dictionary is a catalogue of all data items in a system. The data dictionary stores details.
I Information Systems Technology Ross Malaga 4 "Part I Understanding Information Systems Technology" Copyright © 2005 Prentice Hall, Inc. 4-1 DATABASE.
Physical Database Monitoring and Tuning the Operational System.
CIS 250 Advanced Computer Applications Database Management Systems.
AOIT Database Design Unit 3, Lesson 9 Data Integrity Copyright © 2009–2011 National Academy Foundation. All rights reserved.
Chapter Physical Database Design Methodology Software & Hardware Mapping Logical Design to DBMS Physical Implementation Security Implementation Monitoring.
Access Chapter 2: Relational Database Objectives Design data Create tables Understand table relationships Understand data types, key, & field properties.
History Data Service1 Good Design for Historical source based Databases History Data Service Hamish James.
Physical Database Design Purpose- translate the logical description of data into the technical specifications for storing and retrieving data Goal - create.
CS1100: Data, Databases, Queries Action Queries CS11001Advanced Queries.
© 2017 SlidePlayer.com Inc. All rights reserved.