SSIS will allocate memory from the unallocated system memory for each package executed, and surrenders that memory shortly after the package completes its execution. When planning for memory needs, it is critical to understand how SQL Server Integration Services uses memory. To the question “How much memory does SSIS need?”, the only definitive answer is, “As much as possible.” However, before throwing a lot of expensive RAM at the problem, make sure you know how SSIS consumes memory during package execution. Package design, architecture (ETL versus ELT), and parallelism will all impact memory use, so you have to include those factors in mind when configuring memory for SSIS. However, memory isn’t free, and simply maxing out the memory on every SQL Server running SSIS isn’t palatable for most hardware budgets. Integration Services is an enterprise ETL tool, and works best on enterprise-level memory. SSIS can consume a lot of memory, so give it as much as you can. (Seriously, you weren’t expecting an exact number, right?)
When configuring a new instance of SQL Server running SSIS, or adding SSIS to an existing SQL Server installation, it is important to understand how SSIS uses memory, and what factors in your package design will impact the amount of memory used by SSIS. One of the most common questions I am asked about ETL configuration is how much memory SSIS requires.
0 kommentar(er)
