SSIS: working with Excel source data

I have a large Excel spreadsheet that I want to load into an SSIS package and output relational datasets.

My first throught was to load the data straight into a recordset and then through code and loops, pull out the data into new recordsets.

Next, I've been playing with the Excel source editor and trying to query the Excel data and then intending to just output the query results into recordsets (but I'm receiving the error: No column information was returned by the SQL command).

Which method would be better to work with and how should I go about doing it?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Reza RadConsultant, TrainerCommented:
why you want to feed data from excel to recordset ?
this is not recommended when your excel file is large.

if you want to do operations on data and then feed in table or any other destination, you can use many transformation in SSIS for this purpose and usually you don't need to feed a recordset.

please let me know what you want to do in your data transfer exactly, maybe there be better ways.
The second option would be the way to proceed... Try to use the Query editor to build your query and also check the output on the same window

But then it might take a while to run, let us know what you are trying to do.. to help you better
wppiexpertsAuthor Commented:
the data is a non-normalized dataset...each Excel row essentially contains account data plus 50 columns of historical data. My intent is to pull out data to create header records and detail history records and then upload into a sql database, so my initial thought was to load it into a master recordset and work with it from there, once the data manipulation was done, then load it into the database.

any suggestions (or web articles to follow) that could get me started in the right direction?

Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

My opinion is you may be wasting resources if you load in to a recordset.  

A couple of other options:

1.  Just load the Excel file and manipulate AFTER the load.  Possibly put in to a temp upload table, make modifications, ect.. then migrate to a final destination.  Or load in to final table and use time stamp to massage the just loaded data.

2.  Or use expressions, derived columns, data conversion transformations.

I would avoid recordset as much as possible.  Just not efficient.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
That's right  you don't need to use record sets for doing that.. You can make use of Staging Table(Temp Table), Derived Column for writing expressions and converting Data types and Lookup Transformation (if necessary) ..
Check these links

Let me know if you need more help
wppiexpertsAuthor Commented:
unfortunately, our policy is to not use temp tables, so recordsets are the method I have to work with.
I would still look in to the other ssis transformations.  Will be much quicker. And do the same job.
Honestly, if u r using a recordset, u r defeating the purpose of using ssis.
Reza RadConsultant, TrainerCommented:
I am agree with carsRST which you should use TRANSFORMATION instead of record set,
tell us sample input data and sample output
Regarding your error:

see that the SQL query that you write against the Excel file has aliases for the column names and be very very sure that you use 32-bit. In BIDS you can set the Run64BitRunTime property to false in your project properties. At SQL Server, if it is a 64 bit machine, you must enforce 32-bit. In 2005: calling the package with a cdm command. In 2008: you can select an option in the job step properties to run the package in 32-bit.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.