My Photo

Consulting/Training

Speaking engagement

January 2007

Sun Mon Tue Wed Thu Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31      

My Online Status

Disclaimer

  • No Warranty..
    I have taken care in writing the articles on this blog and make no implied or expressed warranty of any sort. For any errors or omissions, I will not be responsible in any way.

« SSIS: Web Service Task | Main | SSIS: Dynamic file naming »

November 20, 2006

Comments

Bopanna Kallichanda

This helped me. The problem with my package was not having direction = output

ZULFIQAR SYED

Thanks for your feedback Bopanna.

Jesus

hey,I've checked your procedure and it's very interesting...unfortunately, what I'm looking for is using a package inside a visual basic form.Inside the package runs a SP that HAS to use a variable to show the information the user wants,you know what I mean??..I hope so.Anyway,the thing is that I can't find the way to pass this variable through the form to the package so I can see the info I want.Hope you can help me with this.
Thanks. Jesus

sg

is this issue the same for running some SQL Task? I have been using jsome insert and updating commands with parameter using'?' in OLEDB conn but it is throwing a vague error:

[Execute SQL Task] Error: Executing the query "UPDATE dc SET dc.payrollType = dcs.PayrollType, dc.checkDate = dcs.checkDate, dc.periodBegin = dcs.periodBegin, dc.periodEnd = dcs.periodEnd, dc.description = dcs.description , dc.status= dcs.status, dc.frequency = dcs.frequency, dc.emplType = dcs.emplType, dc.emplFilter =dcs.emplFilter, dc.lastETLDate = ? FROM dimCalendarDetail dc inner join DimCalendarDetail_Staging dcs ON dc.co = dcs.co WHERE dc.calendarId = dcs.calendarId AND dc.batch = dcs.batch SELECT @@ROWCOUNT AS rowUpdate " failed with the following error: "Invalid object name 'dc'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

I found couple of blog mentioning it could be because of Service Pack. Now I have new service pack installed (SP 2 for sql2005) and is still showing the same error. Any help will be highly appretiated.

Thanks

Jasmine

this gave me a huge help.thnx a lot

Gonzalo

Hi ...
your problem seems to be in the ", dc.lastETLDate = ? FROM " part of the query...i have the same problem ... and found that the query parser does not allow using the "?" as parameter in the SELECT part of the query. it only permits to parse queries with the parameters in last part of the query as the WHERE condition

hope it helps .

Atul Saxena

Thanks
for the valueble support.
Can u tell me how can I run the same package with different combination of source and destination dyanmically . I want to run the ETL in single shot

Unpro

Finally, a sample that works!!!

but why OLE? Why does my .Nyet fails?...


Laura

Thank you!! You really helped me

Lily

this was the first site of many that defined it clearly and worked first time! thanks! ><

Alan Barber

Thanks very much for this. I couldn't get the syntax for OLEDB right for ages until I read your post. Cheers.

Hamed

Thanks for this great post

Baas

hi
I tried passing a value to a proc with in a OLEDB source but after mapping when I try to parse it gives me an error saying
invalid parameter number
the syntax is

exec proc_name ?,?

Hope you can help me with this. I searched lot of blogs but couldn't find any solution.

Jordan Jumpman

Thanks for this wonderful tutorial. I made this bed for my daughter-dog Candy using her favorite fleese blankets. I used left-over quilt batting pieces for the stuffing. She loved it so much that I made another bed for my niece-dog, who also loved it. Thanks again.

Nike Shox For Sale

Romance: Many women long for the days when they and their husbands were courting.

Nike Shox For Sale

Romance: Many women long for the days when they and their husbands were courting.

texas auto glass

Naturally, if you drive a relatively old vehicle, the value of your vehicle may not justify the cost of fully comprehensive cover.

The comments to this entry are closed.