bizzare behavior from a connection object

  • The connection object is using an expression at run time to get the name of the server to which to execute a select statement. Data flows return error that object does not exist because it defaults to the local instance of SQL. Setting the validation flag to true to attempt to circumvent that check does not work. Suggestions on how to create a select statement on an ojbect for a table that WILL exist at run time but not development time in a data flow needed.....

  • At design time, the object needs to exist. BIDS needs the metadata.

    Once you designed the package, the object doesn't longer need to be there.

    ps: validation should be set to FALSE.

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

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

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