July 12, 2007 at 6:19 am
I have created a package which is transforming the data from Source OLEDB Sql Server to Destination OLEDB Sql Server programatically in VB.NET
During execution phase, I want to generate an event after every 1000 rows are transformed. As per I think, OnProgress event of IDTSEvent doesn't support this kind of a thing.
And after my Transformation is completed, I want to know how many rows have being transformed.
So how can the above two task be performed?
July 13, 2007 at 2:02 am
The easiest way to get a row count is by using the rownnumber component, assign the value to a variable and on post execute, use the variable. As for getting a count every n rows, you might get away with a script component and a custom script but I do not think you can fire events in the data flow due to performance reasons. I might be wrong though.
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
July 14, 2007 at 1:39 am
Thanks for reply.
But I have searched a lot but I can't find the way, how to use row number component progammatically and bind it with TaskHost.
Can you please give me some example in .Net to use the component.
Regards,
Gaurav
July 16, 2007 at 6:43 am
I have added Row Count Component to my package by following code.
Dim DFTransform As IDTSComponentMetaData90
DFTransform = DTP.ComponentMetaDataCollection.New()
DFTransform.ComponentClassID =
"DTSTransform.RowCount"
DFTransform.Name =
"RowCount"
But now i am getting the error "The product level is insufficient for component 'Row Count'" when I execute the package. So what could be missing.
July 16, 2007 at 9:07 am
Three possibilities according to this:
http://msdn2.microsoft.com/EN-US/library/aa337371.aspx
You have installed workstation components but not integration services. Running packages outside Business Intelligence Development Studio requires the installation of Integration Services.
You are using the SQL Server Import and Export Wizard and you have installed Workstation components but you have not installed Integration Services. This problem has been fixed in Service Pack 1 or later.
Your package may be attempting to use advanced components for Analysis Services, data mining, or text mining that are available only in SQL Server 2005 Enterprise Edition.
"Beliefs" get in the way of learning.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply