I can only surmise that this is your blog that you are linking to.

This is making a lot of assumptions here. First of all setting rowcount affects all queries in that connection. Unless you remember to set it back to 0 all subsequent queries will be affected. The bigger issue is that this is not necessarily true. This code is making an assumption that id is an identity column that is always incrementing. If the value for id is set by code or the value is a decrementing identity this code will not return the correct row.

Here is a working proof.

create table employees

(

id int identity(100, -1)

, FullName varchar(50)

)

insert employees

select 'I am the oldest.'

insert employees

select 'This is the ''newest'''

select * from employees order by id desc

By definition you can't have a table with more than 1 identity column. I assume the intention is to state that the table has only 1 column and it is an identity. My argument would be that a table with only a single identity column is not a table and therefore this question is pointless.

While I applaud the effort I am afraid that the questions are not very robust.