SSIS Column Export

  • Comments posted to this topic are about the item SSIS Column Export

  • Jus got lucky!! Nice question though!! πŸ™‚

    ______________________________________________________________Every Problem has a Solution; Every Solution has a Problem: πŸ™‚

  • Never come across this before - thanks

  • I did not had luck πŸ™‚ and did not knew the answer. But thanks for sharing this exercise and the experience.

    Iulian

  • Thanks for sharing.

    Thanks

  • This was removed by the editor as SPAM

  • thought for sure the path was missing from the query was the answer

  • The FileID column does not look like FilePath column.

  • Thanks Andy, something else learnt. And my Wrox 'Professional Integration Services' book was no help at all!!! πŸ˜‰

    Sean

  • Sergei Yakovlev (7/9/2014)


    The FileID column does not look like FilePath column.

    I agree... I see we're back to trying to read Andy's mind to determine what he really wanted to ask instead of what he actually asked. :unsure:

  • Thanks Andy

  • I was thinking about the unicode column requirement, because it is required in some components such as the term extraction component, but then I went for the more logical answer.

    Thanks for the question.

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

  • What's your best guess on what's going wrong?

    This does require you to make the assumption that FileID is probably a numeric of some type, in real life you'd probably get it quickly if you saw the query results, it's harder when you're just hearing/visualing the problem.

    And there's the problem. I am that junior developer, and when questions explicitly ask you to guess and the explanation requires you to make an assumption then I've next to no chance. I enjoy the QOTD, I like the fact the I've usually got to do some research to answer the question and I accept that I'm going to get some of them wrong. What I don't like is when a question requires a level of experience to answer it because the answer is essentially system specific. Obviously some questions are going to be harder than others and the whole point of them is to learn but it seems a little unfair to base the answer to a question on the things that aren't cold hard verifiable facts. Don't get me wrong, I like learning about the in depth workings of SQL Server and that's my point; with the QOTD I like to learn something to get the answer right but it sometimes seems that we're expected to just know something else first.


    On two occasions I have been asked, "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" ... I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question.
    β€”Charles Babbage, Passages from the Life of a Philosopher

    How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537

  • I thought it was a decent question on something I know nothing about. Thanks.

  • Chris Harshman (7/9/2014)


    Sergei Yakovlev (7/9/2014)


    The FileID column does not look like FilePath column.

    I agree... I see we're back to trying to read Andy's mind to determine what he really wanted to ask instead of what he actually asked. :unsure:

    Agree

Viewing 15 posts - 1 through 15 (of 27 total)

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