Viewing 15 posts - 57,541 through 57,555 (of 59,067 total)
I just love it when they don't
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2006 at 6:38 am
Very cool... thank you.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2006 at 6:32 am
I did a bunch of experiments on several different machines (desktop, 4 cpu server, 8 cpu server, etc) about 9 months ago and the results are posted somewhere on this...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2006 at 4:50 am
Serqiy, cool function... especially great for bi-monthly paydays on the 1st & 15th, etc.
Bellefso... this returns the first date of the current month... was in both Serqiy's and my examples...
SELECT --Jeff Moden Change is inevitable... Change for the better is not.
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
September 26, 2006 at 9:41 pm
In a function, instead of (over simplified example)...
..etc..
I use,
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2006 at 9:12 pm
I finally found one at
http://www.sommarskog.se/arrays-in-sql.html
Is your's any better?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2006 at 9:00 pm
I'm still looking for the function that will split a 2gb string on a delimiter, Serqiy... any chance of you posting it or the URL you got it from? Thank...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2006 at 8:41 pm
I wondered when you were going to show up on this one ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2006 at 1:26 am
I agree about the BEGIN/END where no transaction is defined... however, if you check out Books Online, you'll find that BEGIN/END is required syntax in UDF's ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2006 at 1:24 am
Sorry... didn't see Remi's solution, which is obviously spot on! ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2006 at 12:14 am
If this in in a complex GROUP BY, forget COUNT... you have a condition and COUNT isn't going to do it for you... SUM(CASE will....
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2006 at 12:13 am
Not sure how you're using it, but "IF" smacks of Cursors, While Loops, and other forms of "RBAR"... if you really want you code to fly, write it set-based with...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 26, 2006 at 12:08 am
I know it's just an experiment but, ugh... if you end up counting transactions in your code, ya just might have a bigger problem with your application...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2006 at 11:43 pm
First, not sure how you'd do a like with the values "mashed" together even if you were looking at a single column. I can tell you that anytime you can...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2006 at 11:38 pm
Ok.... thought you'd gone nuts on me for a minute
Short naps get me through the day ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2006 at 11:28 pm
Viewing 15 posts - 57,541 through 57,555 (of 59,067 total)