The only way is to lock the whole table while you do the insert so that noone else can read/update from it... can be a pain in the ass if...

SET SHOWPLAN_TEXT ON

GO

Select 'query here'

GO

SET SHOWPLAN_TEXT OFF

Can you post the execution plans?

Do a search for parameter sniffing, you'll see what to do to fix this problem.

... was just wondering.

The problem with this approach is that if you have the tables Users and UsersPermissions and that the view uses the table UsersPermissions, then the like will catch a hit...

How could a pair of date cause a loop in a query???. The condition is either true or false, how can this generate a recursing/looping algorithm of some kind??

We seriously need more info than that : Help us help you

That's the easy part for us >> Good luck .

only "10/3/2005 " is impossible if it's really a smalldatetime column. What does the source data looks like?

Are you talking about the seconds missings or just the lack of...

Sounds simpler .

You'll have to create it in the beforeinsert() event if you want to stop that error... or forbid that they enter data for child, whichever makes sens in your application.

Just a question... How would someone generate such an infinite loop?

Why not block that by forbidding the use of the while keyword in the query?

May I ask what the dateadd is supposed to do in this context?? (DATEADD(M, - 0, GETDATE()))

I C, as I said I never had to do that so I'll trust your tests to know what's the fastest way .