I have a script that I'm running in SQL Query Analyzer and it returns the
correct information. When I set up the DTS package, using the same script
(copy & paste), the DTS package is dropping a couple of records. Based on
other packages I've set up, I don't find any errors and the others work
correctly. Any thoughts or suggestions?

Thank you.

That's an interesting problem. Can you post the script you are using to
return records?
More information will really help out.

--
Simon Worth


"DAL" <DAL (AT) discussions (DOT) microsoft.com> wrote

Any rhyme or reason as to the rows it drops.

It should not drop any rows at all.

Allan

"DAL" <DAL (AT) discussions (DOT) microsoft.com> wrote

The script follows. My first concern was the date parameter in the "Where"
statement as I was notified by my user that a transaction didn't come through
when it should have pulled that night and I thought it may have had something
to do with the date. Taking the date out, the script ran fine in Query
Analyzer showing all records regardless of date (9) but in DTS, it only
transferred 7.

select C.ClientNumber as LoanNumber, C.FrstName, C.LstName, C.StreetAddress,
C.City, C.State, CA.MSACnty, C.ZipCode, C.EMail, L.LogSubject,
L.Date_Created, CP.CreditScore, COA.FrstName AS COAFrstName, COA.LstName AS
COALstName, COA.StreetAddress AS COAStreetAddress, COA.City AS COACity,
COA.State AS COAState, COA.ZipCode AS COAZipCode, COACP.CreditScore AS
COACreditScore
From Clients As C
Inner Join Logs As L
On C.ClientNumber = L.ClientNumber
Inner Join Cases As CA
On C.ClientNumber = CA.ClientNumber
Left Join CreditProfile As CP
On CA.CaseNumber = CP.CaseNumber
Left Join CoApps As COA
On CA.CaseNumber = COA.CaseNumber
Left Join CoAppCreditProfile as COACP
On COA.CoAppNumber = COACP.CoAppNumber

Where Convert(Char(11), L.Date_Created) = Convert(Char(11), Getdate()) and
CA.ServiceType = 'Home Purchase' and L.LogSubject = 'Contour'


"Simon Worth" wrote:

Is date created a datetime column?

--
Simon Worth


"DAL" <DAL (AT) discussions (DOT) microsoft.com> wrote

send the ddl as well for the tables

--
Simon Worth


"DAL" <DAL (AT) discussions (DOT) microsoft.com> wrote

Yes, the date is a datetime column for when the transaction was created on
the system that I'm comparing against the system date. Cutting the time off
allows just for the compare of dates. If the transaction date shows today,
then the transaction gets processed on when the DTS runs that evening. If it
shows yesterdays date, it gets ignored.

"Simon Worth" wrote:

Makes sure that the dates that are being compared in each instance are
actually the same and not just presumed to be the same.

"DAL" <DAL (AT) discussions (DOT) microsoft.com> wrote