Post reply

Why can't I get SSIS to recognize parameters in an OLEDB Source statement?

  • October 11, 2012 at 3:44 pm

    #268420

    Picture will explain all. I can't figure out how to assign a User::Variable in my Data Flow custom source command.

    This works in 2008R2, and it gives me a generic syntax error in 2012. THOUSANDS of people must be doing this already... What am I doing wrong here?

    Thank you!

  • October 11, 2012 at 4:56 pm

    #1548392

    The information supplied in the Provider adapter probably sucks, Even T-Sql queries with Nested subqueries and parameters in the query bomb.

    This is the way to go.

    how-to-use-a-variable-inside-sql-in-ssis-data-flow-tasks.html

  • October 12, 2012 at 2:39 am

    #1548492

    Greg J (10/11/2012)

    Picture will explain all. I can't figure out how to assign a User::Variable in my Data Flow custom source command.

    This works in 2008R2, and it gives me a generic syntax error in 2012. THOUSANDS of people must be doing this already... What am I doing wrong here?

    Thank you!

    I usually use a variable instead of parameters inside the source component. It can be a bit buggy, as you've noticed.

    The article proposed by Ray uses a script task to construct the SQL Statement, but I wouldn't go that for. An expression on the variable itself suffices.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply