Are you inserting like this??

Insert into dbo.MyTable (Col, Col2, Col3) exec dbo.MySP

..cause if you're not specifying the columns of the insert you can have a lot of problems.

I certainly hope you have more than that left in you .

BTW I've already created a report that looks a lot like a calendar (only 1 week at the time). I too will resuggest that you use dynamic sql only...

Can you post the query (at least pseudo-code) so that we can help developping it?

How long does it take to run the query now?

I'm obviously way over my head in this thread... I'll let the gurus handle it.

INSERT dbo.Contacts(compID, first, last, phone, email)

SELECT compID, fname, lname, phone, email

FROM dbo.import_contact IC

WHERE not exists (Select * from dbo.Contacts C where c.compID = ic.compID AND c.first...

When are you increasing the alert count?

The Curse and Blessings of Dynamic SQL

I would strongly suggest a set based solution but this might be a hard one compared to dynamic sql.

http://www.sqlservercentral.com/columnists/sjones/whodoyouhire.asp

The question is more "Why are you designing the table like that instead of having a single date column?".

We can't help you without the trigger code. Can you send us the relevant part of the script?

Nothing's too easy or too hard for us .

Strange, maybe the bookmark lookup cost was too high compared to the scan... Would have too see the ddl and the data to be more sure.

You're right ron k .. I forgot to take in consideration midnight on the 2nd day with the between operator.