Can you name one problem of trigger solution?

And I pretty sure majority of people submitted posts here never read the statement I quoted. And they afraid of using triggers because...

Bad judgement cause by lack of knowledge.

There gonna be as many "inserted" tables as many triggers called by different users. One per trigger being executed. Not visible from anywhere else.

No...

Bad effort because of lack of knowledge.

From BOL:

A trigger is a special type of stored procedure that is not called directly by a user. When the trigger is created, it...

It's good to know there is somebody around who still remembers old man Boltzmann.

DELETE D

FROM Test D

INNER JOIN Test L ON D.KeyID = L.KeyID AND D.DateAdd = L.DateAdd

WHERE D.DateClose IS NULL AND L.DateClose IS NOT NULL

C'mon, it's not an interview, nobody's dead serious.

I just believe it's better to argue and prove (or fail to prove) your point here then make a mistake in real life...

I just searched this forum for "calendar table" and it returned me 133 messages.

I found one of them from Jeff Moden containing script creating calendar table.

Are we searching in different...

They suggested you to create permanent Calendar table.

Have you done it?

I would suggest to add "DBCC UPDATEUSAGE" into that script.

I saw several times negative values returned by sp_helpfiles.

Search this forum for "concatenating".

Choose one of hundreds suggestions.

Clustered index won't help if you use join queries.

And nothing won't help if you don't.

Don't forget, there are 2 sides on interview.

And if you've got a really good guy at another side of the table then it's not only you evaluating him.

Just bad example.

Try this:

DECLARE @One DECIMAL(38,30)

SET @One = 1.0

DECLARE @Eleven DECIMAL(38,30)

SET @Eleven = 11.0000000000000000000000000000

DECLARE @Result DECIMAL(38,30)

SET @Result = @One / @Eleven

SELECT @Result

GO

DECLARE @One FLOAT

SET @One = 1.0

DECLARE @Eleven FLOAT

SET @Eleven...

Don't use orderig in view.

It's really bad for performance.

You can always order records returned by view.

Why?