SSIS Table Split to Excel
Budget: $30 – $250 USD
I have a single SQL Server table and I need a reusable SSIS package that will export it into five separate .xlsx workbooks. Each workbook must hold a different slice of the data, split strictly by rows—not by columns or filters that change the structure.
Here is what I already know:
• Source: one T-SQL table in SQL Server 2019
• Output: five Excel Workbook (.xlsx) files, created in one run
• Logic: the rows decide which file they belong to (for example, row-range, ID groups, or any other row-based rule we agree on)
What I expect from you:
• A ready-to-deploy .dtsx package built in SQL Server Data Tools / Visual Studio that performs the split and export in a single task flow
• Connection managers configured for both SQL Server and Excel, using dynamic expressions or parameters so I can adjust file paths easily
• Brief documentation or a screencast showing where to edit the row-splitting logic and how to schedule the package in SQL Agent
I will test by running the package on my environment and confirming that five Excel 2016-compatible workbooks appear with exactly the intended rows and no data overlap. If that check passes, the job is done.
Here is what I already know:
• Source: one T-SQL table in SQL Server 2019
• Output: five Excel Workbook (.xlsx) files, created in one run
• Logic: the rows decide which file they belong to (for example, row-range, ID groups, or any other row-based rule we agree on)
What I expect from you:
• A ready-to-deploy .dtsx package built in SQL Server Data Tools / Visual Studio that performs the split and export in a single task flow
• Connection managers configured for both SQL Server and Excel, using dynamic expressions or parameters so I can adjust file paths easily
• Brief documentation or a screencast showing where to edit the row-splitting logic and how to schedule the package in SQL Agent
I will test by running the package on my environment and confirming that five Excel 2016-compatible workbooks appear with exactly the intended rows and no data overlap. If that check passes, the job is done.
Related categories:
Visual Basic
Excel
SQL
C# Programming
Microsoft SQL Server
Data Integration
ETL
Database Management