I've done all the reading possible here but keep running into walls. I'm trying to create a package that calls an Oracle function returning a resultset and spits it out into a CSV. I wanted to use this as a bridge into introducing SQL Server as our OLAP/BI solution for our application. However, ifI can't geta simple csv export to work properly, no one's going to listen in regards to basing our entire BI infrastructure on this. I've done similar tasks before using SSIS against SQL Server but Oracle is being an absolute pain and a half. I was able to get the Script Component to work properly, but then we'd have to manually define the columns for each sproc (50 and climbing) and manually populate the scriptbuffer in code. Looking at SQL 2008, it looks like it has support for passing parameters to Sprocs...but the problem is that even with a parameterless function call, SSIS keeps giving an error. I've tried all the suggestions I could find on the web. I don't want to go to the extreme of creating a custom task but if that's what's necessary, I will. In the interim, I will be making a standard windows service that runs this simple scenario for me. Personally, I would have thought thatenabling ETL (read potential data migration)against anOracle data source would have been one of the HIGHEST priorities for the SSIS team. In a similar fashion I was somewhat surprised by the abysmal support of migrating to TFS from other ALM solutions. And no, creating a framework for me to program my own migration tool is not what I call supporting migration. BTW, in case the question is lost in my post, I am asking for help getting this to work. Please

Hi, Can you give me more information about the Oracle setup? Version of Clienttools/ Database? Did you used a Execute SQL Task ? Correct way to call a Store Procedure is {call <schema>.<Proc Name> } Hope to hear from you! Regards, Naween

Hi, Can you give me more information about the Oracle setup? Version of Clienttools/ Database? Did you used a Execute SQL Task ? Correct way to call a Store Procedure is {call <schema>.<Proc Name> } Hope to hear from you! Regards, Naween Did you notice that you are going to wake up a thread from three years ago?!http://www.rad.pasfu.com

Sorry forgot to look at the post date

Hi, Can you give me more information about the Oracle setup? Version of Clienttools/ Database? Did you used a Execute SQL Task ? Correct way to call a Store Procedure is {call <schema>.<Proc Name> } Hope to hear from you! Regards, Naween Did you notice that you are going to wake up a thread from three years ago?! http://www.rad.pasfu.com I said the same thing on another post. They seem to be replying to lots of posts that fall into this category :-)Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt) MCT, MCPD, MCITP, MCDBA Blog: MrWharty.wordpress.com