Viewing 15 posts - 616 through 630 (of 819 total)
I immediately get it right, because I often fall in these kind of errors.
September 6, 2011 at 1:07 am
INSERTED pulls from what is entered into table, not from the select list.
Of course!
August 26, 2011 at 12:47 am
OCTom (8/3/2011)
ronmoses (8/3/2011)
Carlo Romagnano (8/3/2011)
August 3, 2011 at 6:35 am
paul s-306273 (8/3/2011)
DugyC (8/3/2011)
Interesting question, and something definitely to be aware of.Thanks
I'm not convinved that I need to be aware of this.
Interesting question though.
I agree with you.
August 3, 2011 at 3:13 am
EXISTS check if subquery returns ROWS and does not execute EXPRESSION or read column value. So, in this case divide by zero is never executed, but ONE ROW exists.
August 3, 2011 at 2:44 am
I like dirty "solutions". In extreme cases, I know that a way exists. 😀
July 21, 2011 at 12:55 am
I would replace the question "How many rows returned by executing all of the following?" in "How many rows returned by the last SELECT?" and add another answer: "None, because...
July 20, 2011 at 2:49 am
But if that is not the case then the answer should be "There is NO query returning rows."
I agree with you!
July 20, 2011 at 1:33 am
Toreador (6/24/2011)
I wonder which of the following (if either) is more efficient:
select @a = 1 where @b = 0
or
if @b = 0 set @a = 1
The best one seems to...
June 24, 2011 at 9:52 am
Toreador (6/24/2011)
I wonder which of the following (if either) is more efficient:
select @a = 1 where @b = 0
or
if @b = 0 set @a = 1
"if" runs better
declare @d datetime
,@a...
June 24, 2011 at 9:46 am
If the condition of the WHERE clause validates to true then the result set is returned. If it does not, the result set is empty.
This is true only if...
June 23, 2011 at 1:27 am
Do you mean that for SA you get e.g. 2011-05-26 14:15:37 and for CARLO you get 1900-01-01 02:00:00?
Yes, exactly!
May 26, 2011 at 10:06 am
michael.kaufmann (5/26/2011)
Carlo Romagnano (5/26/2011)
1900-01-01 02:00:00.000
Step 1: bad password attempt
Step 2: correct login
I run the query: SELECT...
May 26, 2011 at 6:24 am
-- to see all bad attempts
SELECT l.name, loginproperty(l.name, 'BadPasswordTime')
FROM sys.syslogins l
May 26, 2011 at 2:01 am
In sql2005, I tried with other logins than sa and I get always the following:
1900-01-01 02:00:00.000
Step 1: bad password attempt
Step 2: correct login
I run the query: SELECT loginproperty('carlo', 'badpasswordtime')
The result:...
May 26, 2011 at 1:50 am
Viewing 15 posts - 616 through 630 (of 819 total)