A Microsoft platform for building enterprise-level data integration and data transformations solutions.
Hi Bob-7209 ,
Running the package directly on the server was a good call—that gives SSIS more CPU and memory to work with.
If you need to run it locally, the best option is to tune the Data Flow buffer properties rather than splitting the extract into multiple flows. Increasing DefaultBufferSize (e.g., 50–100 MB depending on available RAM) and adjusting DefaultBufferMaxRows so each buffer holds more rows can reduce overhead significantly.
Splitting by columns isn’t ideal because SSIS doesn’t have a native way to merge column sets back into a single flat file. You’d end up writing multiple partial files and then stitching them together outside SSIS, which adds complexity and usually slows things down.
If buffer tuning still isn’t enough, another option is to let SQL Server handle the export directly with bcp or SQLCMD. These tools are optimized for bulk export and can be faster than SSIS for very wide datasets.
In short: keep the flow intact, push as much work as possible into SQL, tune buffers for local runs, and consider bcp/SQLCMD if you need maximum speed for flat file output.