1cc1213d   
   From: esquel@sommarskog.se   
      
   Ender Karada? (enkaradag@gmail.com) writes:   
   > dont get that "disturbing" on ur solution. i mean ive also used   
   > xxx.DOCUMENTNO=yyy.DOCUMENTNO with my code of OPENXML. and my code   
   > looks disturbing.   
   > document number may not be a unique value (some documents may even   
   > have a null document number) thats why its disturbing me. actually,   
   > this join works for only "inserted" table, so no problem. but that   
   > still makes me disturbing.   
      
   You did not say anything, so I had to make a guess. I find it somewhat   
   problematic - or disturbing :-) that there is no unique in the incoming   
   data. How do you protect yourself against duplicates? Or do you trust the   
   source?   
      
   If there is nothing that uniquely identifies each invoice in the data, this   
   makes about impossible to shred the document in the way I suggested. Maybe   
   it's possible if you use FLOWR operators in XQuery, but I am not going to   
   try that now.   
      
   Then again, what version of SQL Server are you using? Does it have to be   
   XML?   
      
   > /by the way, im not good at english, perhaps im chosing the wrong word   
   > for "disturbing"/   
      
   I took "disturbing" to mean that you did not like it for esthetic   
   reasons.   
      
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Links for SQL Server Books Online:   
   SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx   
   SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)