This is an intermittent problem. it doesn't happen every time the particular ASP script runs.
It appears that the adodb recordset that's processed by the "while !EOF" loop for some reason, sometimes,
decides identical data is _not_ distinct and will duplicate entries -- not the entire file, but somewhere along the way (this last time at "HODA" rec#632)
it then continues to the last entry (total recs ~2300)
Here is an example of the governee recordset select:
SELECT distinct Claims.*, Clients.[Last] AS Last, Payors.Allowed
INNER JOIN Clients ON Claims.ClientID = Clients.ClientID
INNER JOIN Payors ON Payors.TransactionID = Claims.TransactionID
INNER JOIN MCAProcs ON mcaProcs.code=Claims.ServiceID
where Payors.CarrierCode='CLIENT' and Claims.Status='SEEN'
and MCAProcs.noninvoiceable=0 and Clients.ClientCompletelyTermed=0
and cast(Claims.servicedate as datetime) >= cast('1/1/2014' as datetime)
order by Clients.last,Claims.TransactionID
All the tables are essentially static at run time. updates may be occurring but not anything that'd explain a massive burp like this.
I know sql2k is, well, last century. Does anyone know if this was ever an issue addressed by anyone? any service pack? Was it a type of issue ever acknowledged?
I'm as much curious as frustrated. thanks.