Enable Your Employees To Focus On The Core With Intuitive Onscreen Guidance That is With You At The Moment of Need.
Course Of The Month
8 days, 8 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
SSIS - loading different version of excel files
Posted on 2013-11-08
Hello Experts,
I am using SQL Server 2008 - SSIS to load excel files to database.
SSIS excel connection manager, lets you specify which type of excel file, you will be connecting to either xls or xlsx, you can not use one connection manager for both types, this only allows the user to always change an xlsx file to xls, then process it,
Is there a way to dynamically change the connection manager, based on the type of excel file, or should i just have two different SSIS packages called, when a different type is processed.
Say i have 2 files - test.xls and test.xlsx --- i want to process both files without changing excel connection manager info in SSIS.
Any Idea?
Thanks
I am using SQL Server 2008 - SSIS to load excel files to database.
SSIS excel connection manager, lets you specify which type of excel file, you will be connecting to either xls or xlsx, you can not use one connection manager for both types, this only allows the user to always change an xlsx file to xls, then process it,
Is there a way to dynamically change the connection manager, based on the type of excel file, or should i just have two different SSIS packages called, when a different type is processed.
Say i have 2 files - test.xls and test.xlsx --- i want to process both files without changing excel connection manager info in SSIS.
Any Idea?
Thanks
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3 Comments
Your best method to handle this might be a conditional fork. If it is an XLS file, go down this path - if an XLSX file, go down this other path.
Assuming that the entire package does not require the Excel file connection in every step, this would reduce code duplication and the chance that you fix a bug in one package, but not the other.
Assuming that the entire package does not require the Excel file connection in every step, this would reduce code duplication and the chance that you fix a bug in one package, but not the other.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
In the first part of this tutorial we will cover the prerequisites for installing SQL Server vNext on Linux.
Lotus Notes has been used since a very long time as an e-mail client and is very popular because of it's unmatched security. In this article we are going to learn about RRV Bucket corruption and understand various methods to Fix "RRV Bucket Corrupt…
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month8 days, 8 hours left to enroll
615 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.