SSIS Audit Data Task: Adding a row number to the data flow - by M Vega1

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.


2
0
Sign in
to vote
ID 287060 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 7/12/2007 2:48:50 AM
Access Restriction Public

Description

Been able to add an auto incrementing row number using the Audit Data Task would be very useful. The only workaround I can think of is to use two select statements: one that that used the IDENTITY function and inserts data into a temp table and another that retrieves data from the temp table. This workaround has two limitations:

1 – If temp tables are used the OLE DB data source cannot find any column names returned – this is related to ID 285498. A workaround is to use SET FMTONLY OFF before the statements, but if SET FMTONLY OFF parameters cannot be specified.

2 – It can only be used with relational data sources. When handling Flat Files it would be very useful to now the exact row number of any ‘offending’ rows
Sign in to post a comment.
Posted by Microsoft on 8/10/2010 at 4:17 PM
Thank you for contacting us. After analyzing this issue and prioritizing it in the context of our current development plans, we have found regretfully that it does not meet the bar to be included in an upcoming product release. If you feel that you could provide us with more data to change that judgment, we welcome any further information. Your feedback continues to be invaluable to us and we take all your communication seriously. Please continue to contact us with any questions, suggestions and issues as they arise.

     The SSIS Team
Posted by Microsoft on 1/14/2008 at 2:33 PM
Thanks for your feedback, we appreciate it.

This feature request was not addressed for Katmai release. We have placed this issue in the next release planning items. We'll update you when this issue is fixed.

Thanks,
SSIS Team.