July 9, 2014 at 12:07 am
Comments posted to this topic are about the item SSIS Column Export
July 9, 2014 at 12:38 am
Jus got lucky!! Nice question though!! π
______________________________________________________________Every Problem has a Solution; Every Solution has a Problem: π
July 9, 2014 at 1:21 am
Never come across this before - thanks
July 9, 2014 at 1:32 am
I did not had luck π and did not knew the answer. But thanks for sharing this exercise and the experience.
Iulian
July 9, 2014 at 5:22 am
Thanks for sharing.
Thanks
July 9, 2014 at 6:22 am
This was removed by the editor as SPAM
July 9, 2014 at 7:52 am
thought for sure the path was missing from the query was the answer
July 9, 2014 at 8:20 am
The FileID column does not look like FilePath column.
July 9, 2014 at 8:34 am
Thanks Andy, something else learnt. And my Wrox 'Professional Integration Services' book was no help at all!!! π
Sean
July 9, 2014 at 10:46 am
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:
July 9, 2014 at 1:45 pm
Thanks Andy
July 10, 2014 at 1:02 am
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
July 10, 2014 at 1:36 am
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.
How to post a question to get the most help http://www.sqlservercentral.com/articles/Best+Practices/61537
July 10, 2014 at 5:49 am
I thought it was a decent question on something I know nothing about. Thanks.
July 10, 2014 at 6:17 am
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