<div>
Sounds like a <a href="https://msdn.microsoft.com/en-us/library/ee633763.aspx" rel="ugc nofollow">Master Data Services (MDS) </a>project, where 'business owners' are identified and empowered to eyeball and fix all discrepencies of the same data (i.e. customers) from multiple sources.
</div>


<div>
Thanks Jim.<br />
<br />
I've not heard of MDS, but when I started looking following your post it seems to be an enterprise feature. &nbsp;We are on 2012 Standard. &nbsp;Any other thoughts?
</div>


<div>
None that I'd be willing to take a stab at, as the one time I had to write SSIS code to support a Master Data Services (MDS) application I'm still trying to &lt;twitch&gt; recover from &lt;twitch&gt; that. <br />
<br />
If you wanted an SSIS and T-SQL quick and dirty though you could pump data from all six sources into a single table with an source_id column that identifies the source, then create a SP that does = and LIKE comparisons, and kick out anything that does not match. <br />
<br />
Also there are vendors that specialize in verifying/standardizing address info that you could contract with and run your data through. &nbsp;<br />
<br />
Good luck.
</div>


<div>
<blockquote>
We have six different system each with a SQL Server backend. 
</blockquote>
Have those systems similar tables, like a costumer table?
</div>


<div>
Hi Vitor,<br />
<br />
Yes, each system has very similar Customer tables. &nbsp;In fact in several cases the table structure is identical. &nbsp;<br />
<br />
Jim - thanks for input. &nbsp;I had been hoping that SSIS had some kind of &quot;fuzzy&quot; matching which would allow us to match customers if, say 80% of the data matched. &nbsp;It's not an enormous number of records so we can manually wade through it as you suggest. &nbsp;Just didn't want to do this if SSIS provided something designed to help.
</div>


<div>
<blockquote>
Yes, each system has very similar Customer tables. &nbsp;In fact in several cases the table structure is identical. 
</blockquote>
I think MDS is too much complex solution for this. If you could have a <a href="https://msdn.microsoft.com/en-us/library/ms152746.aspx" rel="ugc nofollow">MERGE REPLICATION</a> configured to share the Customer table data between all systems you'll have the same Customer data shared between all systems.
</div>


<div>
Unfortunately that's not an option for us. &nbsp;The DBs are all outside our control other than read-only access. &nbsp;Customers are added, deleted and modified in each of the systems independently of one another.<br />
<br />
We really need a way to link the customers in all the systems. &nbsp;As per response to Jim, we can do it manually but I was hoping there was a tool which we could use to determine customer matches across systems.
</div>


<div>
I'm not aware of a tool like that. Maybe a 3rd party one. Otherwise you'll need to find a manual way to do this since you only have read-only access.
</div>


<div>
That's exactly what I was looking for. &nbsp;Thanks Jim!
</div>


<div>
<div class="content wysiwyg-content">
We have six different system each with a SQL Server backend. &nbsp;Each DB has customer information in nearly identical tables as described below:<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2016/03_w12/1086955/Capture.PNG" target="_blank" title="Customer (70 KB)"><img alt="Customer" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2016/03_w12/800_1086955/Capture.PNG" /></a><br />
Some customer will appear in multiple systems. &nbsp;So &quot;ABC Co.&quot; might appear in System 1 and System 2. &nbsp;We would like to come up with a consolidated CustomerToSystem &nbsp;table linking a customer to the Primary Keys in the respective tables.<br />
<br />
The problem is due to inconsistencies we cannot 100% match the customers by name and address. &nbsp;In System 1, the customer may be &quot;A.B.C.&quot; while in system 2 it might be &quot;ABC Co.&quot;. &nbsp;Are there any SSIS tools to help us match records?
</div>
</div>


Capture.PNG

We have six different system each with a SQL Server backend.  Each DB has customer information in nearly identical tables as described below:



Some customer will appear in multiple systems.  So "ABC Co." might appear in System 1 and System 2.  We would like to come up with a consolidated CustomerToSystem  table linking a customer to the Primary Keys in the respective tables.

The problem is due to inconsistencies we cannot 100% match the customers by name and address.  In System 1, the customer may be "A.B.C." while in system 2 it might be "ABC Co.".  Are there any SSIS tools to help us match records?

Use SSIS to identify matching customers

SQL Server Integration Services (SSIS) is a component of the Microsoft SQL Server database software that can be used to perform a broad range of data migration tasks. SSIS is a platform for data integration and workflow applications. It features a fast and flexible data warehousing tool used for data extraction, transformation, and loading (ETL). The tool may also be used to automate maintenance of SQL Server databases and updates to multidimensional cube data. SSIS replaced Data Transformation Services, which had been a feature of SQL Server since Version 7.0.

SSIS

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

Microsoft SQL Server 2008 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. Major improvements include the  Always On technologies and support for unstructured data types.