Viewing 15 posts - 1 through 15 (of 581 total)
It is obvious that between theory and practice there is required, besides, a middle term connecting them and providing a transition from oneto the other, no matter how complete...
May 17, 2017 at 8:27 am
Randal Burke (11/4/2008)
1) You do NOT have to pass tables to procedures - especially if the data is already stored on a table on disk. You don't even have to...
November 4, 2008 at 4:54 pm
David B (11/4/2008)
I read it the first time. You seemed to say (and therefore like it or not did say) it was about 3D arrays, but the author didn't go...
November 4, 2008 at 4:36 pm
Jeff Moden (11/4/2008)Keep it clean, slick. 😉
Jeff Moden (11/4/2008)
Oh, I do - mens sana in corpore sano old chap.
And, don't blame me if you don't understand what I'm saying. :w00t:
November 4, 2008 at 1:30 pm
Jeff Moden (11/4/2008)No, I don't think the article was about 3D arrays... go back and read what I posted in my first post. ;).
I read it the first time. You...
November 4, 2008 at 1:11 pm
Unfortunately you have wasted your time because the code is utterly worthless. Sorry, but there is no other way to describe it.
November 4, 2008 at 10:52 am
The author just didn't go far enough in showing how to use the...
November 4, 2008 at 8:31 am
What isn't true? I am talking about the limitations on passing table variables, not string representations of arrays, so the link provided seems beside the point.
Can you explain...
November 4, 2008 at 7:05 am
Agree with IanS re the first example. The second one is fine for storing values but is trivial - everyone knows that you can store data in a table or...
November 4, 2008 at 5:10 am
Maybe this has changed in SQL9, but I don't think you can use EXEC @retval = (@sqlstring). If you use sp_executesql (or any other sp) you can catch a...
June 9, 2008 at 4:11 pm
COALESCE with only two parameters is equivalent to ISNULL. I always use coalesce, as it renders isnull redundant, and can be used with more params (it works from left to...
June 9, 2008 at 3:45 pm
I'm sure someone will find a reason why this isn't a good idea, but one way would be:
CREATE PROC proc1 (@param1 int = null, @param2 varchar(1) = null, @param3 datetime...
June 9, 2008 at 3:39 pm
Ryan Riley (5/20/2008)
June 9, 2008 at 3:02 pm
Did the first suggestion fail? I imagine the case statement didn't like the mixed data types - though that could easily be avoided...
Regarding the perennial problem of separating date and...
August 9, 2007 at 4:45 pm
It's because you are changing midnight to 11:59 pm, I should think. Your query is bound to go a bit pear-shaped if you arbitrarily chop a minute off some of...
August 9, 2007 at 4:04 pm