Hi,
Can u any body tell what exactly the purpose of the options Array size and Transaction size at DRS stage->Input tab. what happens if we take transaction size as 0 or 1 any difference.I tried to find thorugh the manulas but i did'nt get .Please let me know.
Thanks in advance.
Regds
array size and transaction size
Moderators: chulett, rschirm, roy
-
irajasekharhexa
- Premium Member
- Posts: 82
- Joined: Fri Jun 03, 2005 5:23 am
- Location: Bangalore
- Contact:
array size and transaction size
Rajasekhar
You should be able to find that information from the Help button inside the stage, I would think. 
Short version:
Array Size is the number of rows read or written at any one time. Properly setting it can improve performance. In other words, an 'array' of records of that size is passed down the link and then processed.
Transaction Size is how many records are written to the target before a commit is executed. Zero means only once at the end if the job doesn't abort. Otherwise, it means every x records.
Short version:
Array Size is the number of rows read or written at any one time. Properly setting it can improve performance. In other words, an 'array' of records of that size is passed down the link and then processed.
Transaction Size is how many records are written to the target before a commit is executed. Zero means only once at the end if the job doesn't abort. Otherwise, it means every x records.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
irajasekharhexa
- Premium Member
- Posts: 82
- Joined: Fri Jun 03, 2005 5:23 am
- Location: Bangalore
- Contact:
my job is doing 2 updates to same table different fileds with 2 links and one connection and 1 odbc stage
when
Array size1=10 and transactionsize1=20
Array size2=1 and transactionsize2=1
it thrwos error odbc coud not position table
Array size1=10 and transactionsize1=20
Array size2=20 and transactionsize2=20
it runs fine why?
when
Array size1=10 and transactionsize1=20
Array size2=1 and transactionsize2=1
it thrwos error odbc coud not position table
Array size1=10 and transactionsize1=20
Array size2=20 and transactionsize2=20
it runs fine why?
Thats should be because of the different transaction sizes you are setting for the same table and its getting locked. Why do you want to do that anyway?mpauls wrote:my job is doing 2 updates to same table different fileds with 2 links and one connection and 1 odbc stage
when
Array size1=10 and transactionsize1=20
Array size2=1 and transactionsize2=1
it thrwos error odbc coud not position table
Array size1=10 and transactionsize1=20
Array size2=20 and transactionsize2=20
it runs fine why?
No need to spam multiple threads with this same question.
What error do you get? What database are you working with? You've said previously that with the transaction size the same on both links it "runs fine". Are you sure you know under exactly what situations you have problems?
Let's start with the actual error and target database...
What error do you get? What database are you working with? You've said previously that with the transaction size the same on both links it "runs fine". Are you sure you know under exactly what situations you have problems?
Let's start with the actual error and target database...
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
database is informix
error message is
[Informix ODBC Driver][Informix]Could not position within a table
it does not occur if we change the transaction size and array size
The jobs has 2 links into one odbc stage each having update statements
to same table but different tables.
both have separate transaction size/array size as 10,20 and 1,1
it fails but
when i change it to 10,20 and 20,20 it works and nor error
error message is
[Informix ODBC Driver][Informix]Could not position within a table
it does not occur if we change the transaction size and array size
The jobs has 2 links into one odbc stage each having update statements
to same table but different tables.
both have separate transaction size/array size as 10,20 and 1,1
it fails but
when i change it to 10,20 and 20,20 it works and nor error