Well we got to be precise, don't we .

Not bad : 20 post, only one message from the starter of the thread .

Or good claws .

Can you post the table definition, sample data and the desired output?? I'm sure there's a better way to do this.

How about?

Select * from dbo.SysObjects where XType in ('U', 'V')

--VS

Select * from dbo.SysObjects O1 where exists (Select * from dbo.SysObjects O2 where O1.id = O2.id and O2.Xtype = 'U' or...

Let's hear it .

I understood that you suggested to keep the trigger as it was... Sorry for the misunderstading .

No fight = I win (didn't you read the article)??

Yes it's weekend, we have a Holiday on the 24th and another on...

What would be the point of having the trigger then??

Just call all the procs in logical order from the same place... Makes less hidden code and can save a few...

And actually I usually use between or @Date2 whenever possible. I try to avoid calculation on fields like the pest... or whereever possible

Thanx for the info... but that was just a mere exemple of the condition .

Maybe some more typing could solve this :

EXEC dbo.QueueCountRefresh

GO

WAITFOR DELAY 00:00:10

EXEC dbo.QueueCountRefresh

GO

... 6 times

I don't even know where to begin. This is not the way a trigger should be coded. Open the books online and check this section : "create trigger"

You'll...

That would be a nice condition to add... and datediff (D, minDate, MaxDate) < 15?

Update YourTable SET Project = Left(FieldName, charindex('.', FieldName, 1) - 1), Departement = Right (FieldName, LEN(FieldName) - charindex('.', FieldName, 1))

You might wanna make sure that the project is numeric in...