February 4, 2011 at 1:42 am
Hello,
i use SSIS 2008 and will transform data through SSIS.
I import Data from a SQL 2008 server with da "OLE DB SOURCE" Object. Then i forwardet it to a script componat as destination and wrote a VB. NET script. Here i transform my data like
w.GeoX = sGeoXData
Now, i will update my row in the sql server table. I think SSIS do it, but nothing happened. My Rows where not Updated.
I read 4300 Rows in my script component, write SSIS every Row directly to the destination back ? Or must i configure any other thing to update my table data ?
I hope you know what i mean and someone can help me 🙂
February 4, 2011 at 11:54 am
I'm not 100% sure from your description what you are doing but here is my interpretation..
1. Pull data from SQL 2008 using OLE DB Source.
2. Using Script component as a destination transform the data somehow.
3. You *want* to update or insert a row somewhere..
Ok, if that is even close to right..
Step 1 is just fine.
Step 2 should be a transform NOT a destination, destination implies that you are done with the pipeline. You could update the data directly from here but I don't see a reason to.
Step 3 - The output from step 2 could go into an OLE DB Command or an OLE DB Destination where the database could be changed.
CEWII
February 7, 2011 at 12:50 am
Hello,
yes, your interpretation is right.
I tested it with a ole db destination, but then, SSIS inserted new rows. But i want to update my Rows.
i could test it with a ole db command.
February 8, 2011 at 2:32 am
What I do in my packages if I want to update the data in the table which I read in already, is to use
a SQL Task, where I call a Stored Procedure in the database, maybe have a look at this way for a solution?
February 8, 2011 at 8:17 am
OLE DB command is slow. If you have a significant number of updates or deletes, it will suffer in performance. I prefer to insert (fast) to staging tables, then perform set based operations as SQL Commands after the Data Flow Task has completed.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply