It is obvious that between theory and practice there is required, besides, a middle term connecting them and providing a transition from one
to the other, no matter how complete...

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...

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...

Oh, I do - mens sana in corpore sano old chap.

in...

I read it the first time. You...

Unfortunately you have wasted your time because the code is utterly worthless. Sorry, but there is no other way to describe it.

Jeff Moden (11/4/2008)

---

Nah... not true... in SQL Server 2005 and up, there's basically no limit to passing arrays...

http://www.sqlservercentral.com/articles/T-SQL/63003/

The author just didn't go far enough in showing how to use the...

Jeff M:

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...

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...

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...

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...

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...

Ryan Riley (5/20/2008)

---

This is shocking to me. I don't mean to pick on you, Jon, but 1) why would you want an error--or even a warning--telling you something you should...

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...

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...