Gift,

You just blew my mind off...

AMAZING.

It is not about the article (which is quite interesting in itself) but the fact you remembered about an obscure message posted several months ago...

Maybe both of you are quite OK...

Scary part is over 30% (at the time of this post) got it wrong. Many QoDs are quite tricky but this one is very basic and really not SQL specific...

That question has one major flaw - it does not take UDTs into consideration.

I could declare a data type DATE as CHAR(5) and then the correct answer would be '09/09'

How...

One reason could be the query you trying to execute takes a long time and the driver is timing out waiting for the response from the SQL Server. The default...

-YES

-NO

-Not Really but...

They better, they are practically the same code. 😀

I was just surprised that we used the same aliases, but I think GSquared code was closer to the requirements:

I want to...

Is this what you need?

UPDATE D2

SET

bool2 = D1.bool2

FROM #detail D1

INNER JOIN #detail D2 ON D1.detailID = D2.sdetailid

AND D1.bool2 = 1

Ooops. GSquared beat me to it. 🙂

SELECT * FROM table

WHERE field UPPER(field) COLLATE SQL_Latin1_General_CP1_CS_AS

yes and no.

The OUTPUT parameters are unrelated values. You can use them for returning data from a single record if you know you are only getting one record at...

As I mentioned before the OUTPUT parameters are not designed to return recordsets. You want your SP to look like this

CREATE PROCEDURE [dbo].[LISTADOCS]

@INTERNOS BIT

AS

SELECT

NUMERO,

DESCESP,

DESCING

FROM DOCS

WHERE INTERNO=@INTERNOS

OUTPUT parameters are not used to return recordsets. SELECT is.

You can combine both in one stored procedure.

Do you have a specific case you would like to discuss or...

It might be as simple as removing the columns from the SELECT list.:-)

(If I read your question properly).

The code would help.

Yes, but I do not remember what setting it is and if you can control it.

I think there are two separate mechanisms for detecting broken connections.

1. If you issue...

If I read your post correctly the 'remote query' timeout is not what we are talking about here. The timeout you mention is used by the SQL Server itself...