@ Rowcount and "set nocount on" problems caused by the order in which the triggers are used

Generally, @ rowcount and set nocount on are used in triggers. However, if you do not pay attention to the order between them, problems may occur. Today, I wrote a trigger that never worked, and I haven't found the cause for a long time. The Code is as follows:

 

Alter trigger [trg_houses_updated]
On [DBO]. [houses]
After update
As
Begin
Set nocount on;

If @ rowcount = 0
Return;

...
End

 

 

The reason may be the set nocount on, so that @ rowcount does not work. Then, I tried to change the sequence of set nocount on and @ rowcount. The modified code is as follows:

 

1 alter trigger [trg_houses_updated]
2 On [DBO]. [houses]
3 after update
4
5 begin
6 if @ rowcount = 0
7 return;
8
9 set nocount on;
10...
11 end