brad.mccollum (3/2/2015)

---

I've done some extensive work over the past year with SSIS for a client, developing a comprehensive series of packages to do ETL and perform other tasks on numerous Excel spreadsheets containing payroll data.

Client has mentioned another side project to query an underlying SQL Server database and export records for each unique plan (the query would pull info. on various payroll plans... Plan "A", Plan "B", etc.) for an entire year to individual Excel spreadsheets. This process would only be run once yearly. Currently, the export of yearly plan data is done manually through the user interface of a supporting third party piece of software and while it's not difficult, the export process has to be manually initiated and repeated for several hundred clients, so it's a large time involvement. They'd like to get this to where it's an automated process that can just be initiated once yearly and a few min. later, they have all of the exported data present in individual spreadsheets for each Plan (A, B, C, etc.).

Is SSIS possibly overkill for this type of functionality? I know an SSIS package can be written to perform this reading of records and parsing/output of individual Excel spreadsheets for each plan's data obtained from the SQL Server query, but I'm not wanting to overcomplicate how this can be achieved by going w/SSIS by default when the functionality could be done more simplistically elsewhere outside of SSIS.

Thanks for any input.