Viewing 15 posts - 4,786 through 4,800 (of 13,872 total)
January 19, 2018 at 10:31 am
January 19, 2018 at 10:29 am
January 19, 2018 at 8:28 am
January 19, 2018 at 8:22 am
January 19, 2018 at 7:44 am
Most of the people on this forum speak English. If you are able to translate your question to English, you will get more responses.
January 18, 2018 at 2:24 pm
January 18, 2018 at 11:38 am
Instead of this
WHERE NOT ((@OldValue IS NULL AND @NewValue IS NULL) OR (@OldValue = @NewValue))
Try this
WHERE NOT EXISTS (SELECT @OldValue INTERSECT SELECT @NewValue)
January 18, 2018 at 11:16 am
I have spend lots of time reading the articles but not finding it very conclusive....
January 18, 2018 at 10:37 am
January 18, 2018 at 10:25 am
January 18, 2018 at 10:01 am
Below is my requirement. I have given the one material number YHE30B21S as...
January 18, 2018 at 9:51 am
I have a unique situation where i need to execute all the SQLs sitting in...
January 18, 2018 at 9:39 am
^^ I agree with John.
Note that there is no need to precede a THROW statement with a semicolon.
January 18, 2018 at 5:21 am
Standard practice is to use Don't Save Sensitive and then use SSISDB environment variables to pass sensitive parameter values.
January 17, 2018 at 2:03 pm
Viewing 15 posts - 4,786 through 4,800 (of 13,872 total)