Are you sure??

if the dates are like this :

X 2005-03-02 11:27:43.000 2005-03-02 11:31:00.000

X 2005-03-04 09:59:54.000 2005-03-04 10:03:13.000

X 2005-03-07 15:23:58.000 2005-03-07 15:24:59.000

X 2005-03-07 15:23:58.000 2005-03-07 15:24:59.000

the in clause will be...

Also are all those left joins necessary?? You know that you force the server to do a lot more work when using outer join than inner joins?

go in Results in text mode then run this :

SET SHOWPLAN_ALL ON

GO

Select * from dbo.YourView

GO

SET SHOWPLAN_ALL OFF

Hmm, the only thing I can say about this error, is that you have a cursor opened, and then the table was modified somehow by another process.

Is this a recurring...

Re: smalldatetime (just relooked at the date ). Anyways with that little calls I wouldn't expect it to be a real big problem.

The only problem with that query is that you might have a tie... or multiple calls at the same miliseconds so once in a while you might actually get the...

Great!! so you should be smooth stailing from here on out.

Can you paste the query in here... maybe we'll be able to spot something you haven't thaught of yet. Also the execution plan would hurt

I think he meant something like this :

...

From Customer c1

...

WHERE Customer.custSegment='Retail'

AND Customer.campaignId='43'

AND Customer.IsActive='1'

AND CampBaseRep.Owner='1'

And Customer.StartCall IN

(Select top 3 StartCall

From Customer c2

...

Do you know which statement in the proc causes the delay?

You could print out the time needed to executed each part of the proc and then find out which query...

Can you rerun the proc in query analyser with the parameters that fail?

Have you check for a bottleneck on the execution plan?

One query in a while could also be caused by a lock. Have you run the profiler to find such...

Hehe .

Are the stats up to date?

sp_updatestats

Are the index fragmented?

Always a good idea to send out new ideas .