Triggers on tables execute only if at least ONE row is affected. So, explanation is wrong.

WOW64, I learned something new!

😀

From BOL:

MERGE

[ TOP ( expression ) [ PERCENT ] ]

[ INTO ] <target_table> [ WITH ( <merge_hint> ) ] [...

That's true!

😀

+1

What do you mean with "we can use print and exec commands in single query"?

Nice question!

Thanks!

😀

I don't like qotd too long.

But, BOL states that with SERIALIZABLE isolation level:

Other transactions cannot insert new rows with key values that would fall in the range of keys read...

sp_rename leave unaltered the definition, (see sys.syscomments)

create procedure My_proc

as

select 1 as a

go

SELECT * FROM sys.syscomments

WHERE object_name(id) = 'My_proc'

go

exec sp_rename My_proc,Myproc

SELECT * FROM sys.syscomments

WHERE object_name(id) = 'Myproc'

After the rename the definition...

+1

Wonderfull!!!

It, also, works with subquery:

SELECT * FROM (

SELECT MAX(object_id) AS ID,MAX(name) AS NAME FROM sys.objects

) AS o

But in this case it states a wrong type for column NAME(int,null)

I noticed it for columns, tables and functions, but I happily surprised for star!

Good!

😀

A little variation:

-- this runs

DECLARE @i int = 1, @j-2 int = 2;

SET @i += 2;

SELECT @j-2 * @i

GO

-- this raises error

DECLARE @i int = 1, @j-2 int = @i...

Hugo, you always are the NUMBER ONE!

😀

WOW, another qotd with a special offer with "SUMMER POINTS"!

😀