June 17, 2010 at 7:29 am
Can you give us the exact error message?
Does SSIS complain or SQL Server?
If the latter is true, you may want to start SQL Profiler on your target database and see if a query comes in and how it looks like. Then just pick the query and try it in SQL Management Studio.
WM_JUSTMY2CENTS
Guenter
June 17, 2010 at 10:09 pm
I am getting the error as follows:
"Either the input parameters or Resultset is not set correctly".
I am not able to understand where the error is.
-Anuya
June 17, 2010 at 11:35 pm
Have you tried running the package with the SQL Profilter active? This often gives you a hint where the problem lies (e.g. misspelling of a SQL keyword).
June 18, 2010 at 12:10 pm
The best way to use Execute SQL task is to have the SQL statement as an expression.
Whatever parameters you want to pass should be declared as user variables.
In the execute sql task editor, open the Property Expressions Editor.
Chose the property of "SQLStatementSource" to be configured.
Open the expression builder and enter the query in the expression--
Example:
"SELECT * FROM EMP where ENAME = '"+ @[User::EmpName]+"'"
Here EmpName is a user variable of String Type.
Using Property Expressions work with any type of connection.
------------------
Why not ?
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply