Does the servicepack of the client tools matches the one of the sql server?

Welcome back.

Try the sample at http://support.microsoft.com/kb/q194792/.

Apparently there must be a recordset in order to capture the returncode.

Since it is a windows 2000 standard edition, programs cannot allocate more than 2 gb.

To see how much ram sql server consumes, use the performance counters sql server provides.

The /3gb is missing.

What edition of windows 2000 server is it? Standard, advanced ...

Upper/lower case doesn't matter?

Is this only the first time or every time the query is run?

Oops, forgot to specify the field where the values should go into.

INSERT INTO #tmpFeatured (ListingID)  -- (Line 3)

SELECT ListingID from tblListings_Residential_Featured ORDER BY NewID()

select [name],sum(datediff(n,logout,login)) /*total amount of minutes*/

from mytable

group by [name]

order by [name]

You can format the amount of minutes in your report or with a userdefined function.

That is a huge difference. Could it be the amount of data returned?

Query analyzer displays the results faster in grid than in text mode.

What is the connection technology to sql server...

assuming listingid is the primary key

Step 1:

Create a temporary table with an idenity field (listingid, autoid)

INSERT into mytemptable

SELECT ListingID

from (SELECT ListingID from mytable order by newid)

Step 2:

update mytable

set displayorder=autoid

from mytable...

I wasn't aware of that one.

Good you've found it.

*Is it possible that a bad query to cause this behaviour

I can't say for sure. There is an issue with superfast I/O where a query can monopolize I/O access...

Got puzzled again.

Do you wish to capture 1/0 (the exit code)

or the number of failed attempts?

Instead of reading a file byte per byte (1 I/O per byte) , a program can read them in chunks of y bytes (1 I/O command for y bytes in total)

The same...

Simply because there is no recordset in sp_IsValidLogon, just a return code.

You want to capture the exit code?