SSIS Data Profiling Task - support non-SQL ADO connections - by Mike Honey - Manga Solutions

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 766666 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 10/8/2012 8:42:52 PM
Access Restriction Public

Description

The SSIS Data Profiling Task and Data Profile Viewer are very valuable tools.  Unfortunately they are currently limited to source data that exists in Microsoft SQL Server.  In a common integration scenario, the source data is being pulled from another source (e.g. Oracle) into a target of SQL Server, so the Data Profiling activity should be carried out against the source data.  By the time you have already extracted the data into SQL Server, the Data Profiling activity is either redundant, much less useful, or implies rework.
Sign in to post a comment.
Posted by Microsoft on 1/18/2013 at 1:05 AM
Hi, thank you for your feedback. We have investigated the need to support non-SQL ADO connections. The scope and impact of supporting this does not meet our criteria at this point.

Posted by Microsoft on 1/18/2013 at 1:05 AM
Hi, thank you for your feedback. We have investigated the need to support non-SQL ADO connections. The scope and impact of supporting this does not meet our criteria at this point.

Posted by Mike Honey - Manga Solutions on 10/10/2012 at 7:53 PM
It would also be very helpful to be able to send a SELECT statement to the Connection. This would allow filtering of the rows and/or columns to streamline or be more specific. It would also consolidation of Data Profiling Tasks when Profiling a normalized database - multiple tables could be joined together.