P. 1
SAP Business Objects Data services Designer Guide

SAP Business Objects Data services Designer Guide

|Views: 38,664|Likes:
Published by anuragsharma83

More info:

Published by: anuragsharma83 on Mar 25, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

09/16/2015

pdf

text

original

Target tables in real-time jobs support transactional loading, in which the
data resulting from the processing of a single data flow can be loaded into
multiple tables as a single transaction. No part of the transaction applies if
any part fails.

Note:

Target tables in batch jobs also support transactional loading. However, use
caution when you consider enabling this option for a batch job because it
requires the use of memory, which can reduce performance when moving
large amounts of data.

SAP BusinessObjects Data Services Designer Guide 319

13

Real-time Jobs

Real-time source and target objects

You can specify the order in which tables in the transaction are included
using the target table editor. This feature supports a scenario in which you
have a set of tables with foreign keys that depend on one with primary keys.

You can use transactional loading only when all the targets in a data flow
are in the same datastore. If the data flow loads tables in more than one
datastore,targetsineachdatastoreloadindependently.Whilemultipletargets
in one datastore may be included in one transaction, the targets in another
datastores must be included in another transaction.

You can specify the same transaction order or distinct transaction orders for
all targets to be included in the same transaction. If you specify the same
transaction order for all targets in the same datastore, the tables are still
included in the same transaction but are loaded together. Loading is
committed after all tables in the transaction finish loading.

Ifyouspecifydistincttransactionordersforalltargetsinthesamedatastore,
the transaction orders indicate the loading orders of the tables. The table
with the smallest transaction order is loaded first, and so on, until the table
with the largest transaction order is loaded last. No two tables are loaded at
the same time. Loading is committed when the last table finishes loading.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->