November 3, 2017 at 6:01 am
HI Champs,
How many child packages can be called inside master package ? is there any limit for that ? how many can be called in parallel ?
because am getting out of memory issue . am having around 27 child package in one master package. other than reducing the no what else can be done ?
Regards,
Ravi
November 3, 2017 at 6:08 am
ravi@sql - Friday, November 3, 2017 6:01 AMHI Champs,
How many child packages can be called inside master package ? is there any limit for that ? how many can be called in parallel ?
because am getting out of memory issue . am having around 27 child package in one master package. other than reducing the no what else can be done ?
Regards,
Ravi
It would seem that available RAM is your limit, regardless of any overarching absolute limit, which is presumably little more than an academic question in your case.
Try using multiple SEQUENCE containers in series to limit the number of packages which can execute in parallel.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
November 6, 2017 at 6:57 am
ravi@sql - Friday, November 3, 2017 6:01 AMHI Champs,
How many child packages can be called inside master package ? is there any limit for that ? how many can be called in parallel ?
because am getting out of memory issue . am having around 27 child package in one master package. other than reducing the no what else can be done ?
Regards,
Ravi
While what Phil is saying is a good idea, it may just hide the real issue. The question is whether each such package is being reasonably efficient with it's use of resources, like RAM. I'd be looking to see just how much RAM each of these packages is using, and also asking just how much RAM is on the SSIS box that you're actually running out... Another possible scenario is that you are processing too much data in a package that runs in 32 bit mode, and thus is limited to an address space of at most 4 GB, and possibly only 2 GB, depending on the exact circumstances. If you provide significantly more detail, we might be able to help address efficiency and/or provide you the kind of logical reasoning needed to convince management to get more RAM.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
November 6, 2017 at 7:03 am
sgmunson - Monday, November 6, 2017 6:57 AMravi@sql - Friday, November 3, 2017 6:01 AMHI Champs,
How many child packages can be called inside master package ? is there any limit for that ? how many can be called in parallel ?
because am getting out of memory issue . am having around 27 child package in one master package. other than reducing the no what else can be done ?
Regards,
RaviWhile what Phil is saying is a good idea, it may just hide the real issue. The question is whether each such package is being reasonably efficient with it's use of resources, like RAM. I'd be looking to see just how much RAM each of these packages is using, and also asking just how much RAM is on the SSIS box that you're actually running out... Another possible scenario is that you are processing too much data in a package that runs in 32 bit mode, and thus is limited to an address space of at most 4 GB, and possibly only 2 GB, depending on the exact circumstances. If you provide significantly more detail, we might be able to help address efficiency and/or provide you the kind of logical reasoning needed to convince management to get more RAM.
Good point. The design of each package is an important factor. If they're doing lookups or aggregations, for example, RAM usage is likely to be heavy regardless of parallelism.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply