Duration - Import request in QA

[Former Member]

Hi, I have around 4 cubes, 3 ODS objects pulled with grouping option as "DATA FLOW BEFORE" in a transport which is being imported in QA system. It is running since more than 2 and half hours.

I would like to know how much time does it generally take to import the request, with the size as mentioned above?

What are the possible reasons why an import would run for so long?

How do I trace the import process to check that this long duration is for gud and not because of something went wrong?

Any inputs on this wud be really helpful.

NOTE(this request is from a newbee)

Thanks in advance

[Former Member]

Hi,

If these are new objects, they won't take long. But, if you are modifying existing Cubes or ODS and if there is data in those objects in the target system, it'll take time to transport depending on the amount of data you have. Best case would be to transport each one individually and check how long it takes for each object.

Cheers,

Kedar

[Former Member]

Hi, Thanks for the reply.

In this case, we are importing new objects. But the problem here is the related objects of these news are also getting pulled into this request. These related objects has the data in QA system. But for how long this request would run?

Ex: CUBE1, ODS1 and ODS2 are pulled. But the infoobjects being used in this cube/ODS objects are referred by few other ODS objects which are already in QA with the data in them. I'm not able to avoid this extra ODS objects even with the grouping option "NECESSARY OBJECTS".

What is the general import time for a scenario like this?

A gud transport request, which can get imported fast, should ideally have how many objects?

DO we have tot ake any precautionary measures to avoid this part from splitting the objects into diff requests.

A list of general gud practice points in transports wud give me gud lead.

Thanks