Ben What you're not making clear is how you can identify the 'incomplete' transactions. IF you could suppose that there was a WHERE clause that would define those rows, and IF you could import the other, COMPLETE data into a new table, then we could help you!
For example, if the COMPLETE data were in table NewTable with a PK column PKID, and the same column is in the table that is INCOMPLETE (table OldTable), then the "missing transactions" would simply be: SELECT * from NewTable WHERE PK_ID NOT IN (SELECT PK_ID FROM OldTable) I suspect it's not that simple, but you're not giving us any more information to work with! David Blocker [EMAIL PROTECTED] 781-784-1919 Fax: 781-784-1860 Cell: 339-206-0261 ----- Original Message ----- From: "Ben Fogt" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[EMAIL PROTECTED]> Sent: Tuesday, July 27, 2004 11:46 AM Subject: [RBG7-L] - Joins? > Being fairly new to SQL and everything, it looks like I'm going to need to > see if there's an easier way to do something with a join instead of a > complicated series of temp tables. Here's the situation. > > Found out that some data that we received and processed was incomplete. I > have the correct data now in several files. What I need to do is create a > list of everything missing from our imports and eventually use that list to > process just the missing transactions. > > From what I know about Outer Joins (very limited) it doesn't look like it > would do what I need. Is there something that would make this quick? We're > looking at about 30,000 transactions and the table missing transactions is > over a million rows. > > (David, I've got your book, but it's at home. I promise I'll read > everything as soon as I fix this!) > > Thanks for any help. > > Ben Fogt aka "The Shark" > >
