January 10, 2014 at 1:08 am
Hi Everyone,
I want to update the table in a database, performance vice which transformation is best to use?
Thanks in advance.
sharmi
January 10, 2014 at 1:10 am
sharmili.net (1/10/2014)
Hi Everyone,I want to update the table in a database, performance vice which transformation is best to use?
Thanks in advance.
sharmi
"Vice"? What is that?
January 10, 2014 at 1:34 am
sorry for typo..wise which means performance point of..
January 10, 2014 at 1:40 am
Inserts are best done using a dataflow.
Updates are best done as a set-based operation - meaning that the OLEDB command is NOT the way to go. One possibility is funneling all of your inserts to a staging area and then finally running a T-SQL UPDATE or MERGE from that to the target table.
January 10, 2014 at 1:41 am
Do not use the OLE DB Command Transformation.
Write the change rows to a staging table and then use an Execute SQL Task to issue an UPDATE statement.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 10, 2014 at 1:48 am
Thank you for your responses..
January 10, 2014 at 1:53 am
why should not use OLEDB cmd since its processing each row..or any other specific reason is there?
January 10, 2014 at 1:55 am
sharmili.net (1/10/2014)
why should not use OLEDB cmd since its processing each row..or any other specific reason is there?
That is the reason.
January 10, 2014 at 1:58 am
sharmili.net (1/10/2014)
why should not use OLEDB cmd since its processing each row..or any other specific reason is there?
Row by row == slow (very slow for large data sets)
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 10, 2014 at 3:44 am
Then what is the purpose of using OLE DB transformation as it causes performance issue when we have execute sql task.
January 10, 2014 at 4:17 am
sharmili.net (1/10/2014)
Then what is the purpose of using OLE DB transformation as it causes performance issue when we have execute sql task.
The performance is reasonable for small data sets (just a few rows, less than 100).
It's the same as a cursor in TSQL. It's damn slow, but sometimes you need a cursor.
(and there are other components in SSIS who are just not useful at all)
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 11 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply