Rowcount

Question

Post reply

Rowcount

January 29, 2010 at 2:49 am

This was removed by the editor as SPAM

Viewing 15 posts - 31 through 45 (of 132 total)

You must be logged in to reply to this topic. Login to reply

vk-kirov SSCertifiable Points: 7686 More actions · Answer 1

honza.mf (1/29/2010)
And what about the answer "Any number, 1" or better "Nonnegative number, 1".

Agreed 😎

Simon Liddle SSCrazy Points: 2580 More actions · Answer 2

It seems to depend on the client tool, not the server - I tried this with both QA and SSMS against a SQL 2000 server - QA returned 1,0 as per the "correct" answer, SSMS returned 1,1.

I answered before trying the script and got it right, tried the script in QA and saw that agreed, but only tried SSMS after reading the discussion.

As to suggestions about trying against different versions, bear in mind that the question might have been contributed by someone without easy access to anything above 2000 or may have been submitted a long time ago. In fact, I would never have fired up SSMS to test against my 2000 Server if it hadn't been for the discussion that came about because the answer was ambiguous! 😛

Matthew Saggers-700210 SSC Enthusiast Points: 183 More actions · Answer 3

I have tried this on a few severs now and on a few different version and still get 1,1

Is this right?

Marko Frkovic Ten Centuries Points: 1096 More actions · Answer 4

Marko Frkovic

Ten Centuries

Points: 1096

January 29, 2010 at 1:55 am

#1110545

Got (1,1) on 2000

simon.whale Ten Centuries Points: 1393 More actions · Answer 5

if i do as the question says i get the answer 1,1

but if i do

set nocounton

select @@rowcount

i then get the answer given

Simon Liddle SSCrazy Points: 2580 More actions · Answer 6

Just to take this one step further from my previous comment about it depending on the client tool....

If you profile QA as you connect to the server, you will see that the last statements executed by QA on opening a new window (connection) are SET statements which configure the connection settings (ansi_nulls, nocount, quoted_identifier, etc.) so @@ROWCOUNT when you have a new blank QA window is 0.

In contrast, when you profile SSMS, you'll see that the last statements to execute are SELECT statements (in my case, they are capturing my spid and the SQL version). In this case, the @@ROWCOUNT when you have a new blank query window open in SSMS is 1.

simon.whale Ten Centuries Points: 1393 More actions · Answer 7

that is the issue as i ran the queries on SQL2005 std edition

tomasiranek SSC-Addicted Points: 429 More actions · Answer 8

I have same experience on few servers - 1,1. It really depends on previous commands and if non commands were run, than it is 1,1, so you should change the correct answer.

rwlpalmer Valued Member Points: 71 More actions · Answer 9

As the question is currently posted there are two correct answers.

If you run a statement with no rowcount and then run the query you get (0,1) but if you run the query in a new query window then you get (1,1).

The sql should have been:

SET <some option>

select @@ROWCOUNT

Think it must be that establishing a query window causes some operation that sets the @@rowcount to one (insertion of the allocated spidid into the sys tables?). Hence the two answers that people have observed.

rene-500237 Hall of Fame Points: 3769 More actions · Answer 10

I got 1,1. Ithink the qod should be more precise.

Thanks

kaspencer SSCarpal Tunnel Points: 4880 More actions · Answer 11

Well, well, well, yet another complaint about a QotD, and I am not the only one!

Like so many others, I was inclined to go for 0,1 but I just thought I'd run it first to see whether I was right - and yet again someone has asked a question that does not always produce the same result.

So, if you are considering writing a QotD, just remember: you are under a definite obligation to ensure that the answer is predictable and will be produced on the vast majority of instances and versions (unless conditions are specifically mentioned).

And Editors: how about fining the writers of bad questions - demoting them by two ranks eh? That'll teach 'em!

Kenneth Spencer

You never know: reading my book: "All about your computer" might just tell you something you never knew!
lulu.com/kaspencer

honza.mf SSCertifiable Points: 5519 More actions · Answer 12

As to suggestions about trying against different versions, bear in mind that the question might have been contributed by someone without easy access to anything above 2000 or may have been submitted a long time ago.

Really? Someone without access to anything above 2000? Maybe, but is this enough to submit a valid question? Why not to mention "in SQL 2000" in the heading of the question?

I'm not sure about the age of questions, but are they older than a year?

honza.mf SSCertifiable Points: 5519 More actions · Answer 13

kaspencer (1/29/2010)
And Editors: how about fining the writers of bad questions - demoting them by two ranks eh? That'll teach 'em!

And back again: What about trying the script by editors? Yes, it's a work, but isn't it less work compared to reseting points, changing question, changing answer, resubmitting points and other tricks used in similar cases?

I'm pretty sure editors have access to as many versions of SQL Server as needed.

jshailendra SSCrazy Points: 2260 More actions · Answer 14

Initially thought it would be (0,1) then I was in dual mind in (0,1) and (1,1) finally I executed in Fresh Query Window in 2008 and got (1,1).

Amit,

Can you share your screen shot how you get (0,1). Hope you will not SET NO COUNT ON and then show us the result. 😀