You don't really compare nulls per se, something is either null or is not null. If you are asking how one can detect nulls, there is the IsNull() function you can use. Also, if you have a situation where a 'blank' field or an empty string gets treated like a null as Oracle is wont to do, then you ne...
You'll need to break the job down into component pieces to isolate where any bottleneck occurs. First thought would be to, if you can, add an @FALSE constraint so that no output is written. That way just the input / lookup speed can be gauged.
The warning means you are attempting to write a hashed file record with NULL key values. You need to ensure that does not happen, either by supplying a default value when null or using a constraint to filter them out.
Just in case this confuses anyone, the posted block of text is pretty darn old and came out shortly after SP2 did in 2004. There is no longer any such recommendation to 'not install Service Pack 2' as the patch that corrects this has been available for quite some time.
Could you please post a better picture of your job? I've got no idea if the Nested stage (or anything else) is inside the loop or not and I'd rather not assume. Also post the Trigger expressions on your jobs and the triggers used in the Nested stage. Any jobs finish other than 'Finished OK'? What ab...
There are several, problem is the various parts of the technique seem to be scattered around in multiple posts. I know what's involved but couldn't really find everything laid out all at once. Here is one decent example that I could find. Other suggested Exact Match search keywords for you: multi-ro...
First off, we've got no clue what your job is doing because you haven't given meaningful names to your stages and links. XML_Output_16 DSLink6 DSLink9 What can we infer from that? Nothing. Let's start with basics. Did you import the metadata for your target XML file? Doing so would have generated th...
You might want to check your After SQL tab and make sure nothing is there. I've seen goofy things like that when a space ends up getting put in it by accident.
Then you need to look in the job's log to see what kind of messages are there. You may not be generating any output if your XPath expressions are invalid. This may not even cause any warnings - look at all the messages and see if anything seems to be indicating a problem.