Yes, that is true. I was wondering how "code" could be wrong but didn't notice that you had specified your SELECT explicitly. Usually the query that DS generates by default is good enough. Sorry about misdirecting you.
Do you mean "Fully Generated SQL Query".
But I couldnt see any SQL, If I select that option. Is it usual?
More over can I select only few columns using this option.
Or do you have any other suggestion?
May I know, what do you mean by "query that DS generates by default"?
Is it by the option "Fully Generated SQL Query" in the Query type on SQL tab?
If that is the case, I should need to click on Build, and select the tables which I should have been imported already. Even then, the select query comes with <instance>.<tablename>, where we might change it frequently.
Sorry, Iam new to this version, so not sure about the option that has been widely used.
No, it was just the classic problem when people use their own sql instead of letting the stage generate it for them. Column order doesn't match the DML or the number of columns doesn't match the number in the DML or not all values are bound or key fields aren't marked correctly, or...
What Arnd meant is that these stages will generate the SQL for you by default. You have to specifically change it to 'User Defined SQL' and I've never understood people's some fascination with doing everything as user defined. I constantly have to whack folks for doing that for no good reason.
ps. I never use the 'Fully Generated' option, perferring the 'Generate from the Columns' approach. Note that these names changed in the latest releases.
-craig
"You can never have too many knives" -- Logan Nine Fingers
But my worry is, when I use those option, I get <instance>.<tablename> in the generated query (as I mentioned earliar.)
If i move the job from Dev to PROD wont this be affected?
PS: CODE is just an example. sorry for the confusion.