Finding Sequences (Need help ASAP)

Question

Finding Sequences (Need help ASAP)

Viewing 2 posts - 91 through 91 (of 91 total)

You must be logged in to reply to this topic. Login to reply

Evil Kraig F SSC Guru Points: 100851 More actions · Answer 1

Sorry for the slight necro, was a heck of a 2 weeks and catching up on some older stuff.

Jeff Moden (10/16/2010)
I just ended up writing about it in a very pro QU way and that's why I take a lot of heat about it.

Bah, it's a perfectly valid thing when you're coding in the 'now', not the 'eventually whatever'. Our jobs are accuracy and speed, in that order. Whatever I can get my hands on to do just that will be not only used, but abused. 😀

Can I take it that some of your "wilder, not-so-safe-if-not-done-just-so, coding mechanics" still hasn't caused you a problem with the QU? It's amazing how well things work when you're trying to make something work instead of writing code to make something break. 😀

If I install all the rules you use, no, I don't break anything. But I do use a few tricks, like self-joins to the same table, that won't break it either... well, usually. I've occassionally shot myself in the foot when trying to manipulate fields out of order for the index in the second join. Dates in particular usually require some funky footwork to make the clustered index work exactly right if I'm multi-joining.

One of the things I have found though, in regards to joins, that a second or third temp table that's left heaped can save you a lot of grief for secondary joins. The optimizer resorts the heaps to your clustered index off the first table (caveat: For the few times I've needed to do it. YMMV) and you can get away with some rather risque stuff.

- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA

Jeff Moden SSC Guru Points: 1004402 More actions · Answer 2

Thanks for taking the time to write that feedback, Craig.

Bah, it's a perfectly valid thing when you're coding in the 'now', not the 'eventually whatever'. Our jobs are accuracy and speed, in that order. Whatever I can get my hands on to do just that will be not only used, but abused.

Very cool. Whenever it happens, it's nice to see others that also belong to the "Least likely to use ANSI code" club where the mantra is, "Make it work, make it fast, make it pretty... and it ain't done 'til it's pretty." --Jeff Moden circa a long time ago 😛

--Jeff Moden

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.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)