Viewing 15 posts - 46 through 60 (of 375 total)
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...
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
August 20, 2009 at 7:47 am
A co-worker just couldn't read a query of mine yesterday, so there is something wrong with at least one of us, him and/or me!
Maybe both of you are quite OK...
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
August 20, 2009 at 7:37 am
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...
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
August 20, 2009 at 7:09 am
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...
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
July 1, 2009 at 8:28 am
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...
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
May 5, 2009 at 9:39 am
Respond:
-Does this whole mess make sense?
-Can you set permssions (ie GRANT SELECT) on a connection rather than a user name?
-Does SQL support session variables of some kind?
-YES
-NO
-Not Really but...
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
April 29, 2009 at 1:50 pm
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...
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
April 29, 2009 at 8:14 am
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. 🙂
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
April 29, 2009 at 7:47 am
SELECT * FROM table
WHERE field UPPER(field) COLLATE SQL_Latin1_General_CP1_CS_AS
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
April 29, 2009 at 7:06 am
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...
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
April 24, 2009 at 2:31 pm
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
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
April 24, 2009 at 2:04 pm
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...
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
April 24, 2009 at 11:15 am
It might be as simple as removing the columns from the SELECT list.:-)
(If I read your question properly).
The code would help.
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
April 24, 2009 at 11:11 am
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...
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
April 24, 2009 at 11:05 am
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...
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
April 24, 2009 at 10:06 am
Viewing 15 posts - 46 through 60 (of 375 total)