• SAinCA (5/9/2012)


    Jeff Moden (5/9/2012)


    sherifffruitfly (5/8/2012)


    As for the pissing match - meh. There's times to use stuff and times not to. Never been a fan of the religious fanatics on either the ALWAYSUSEIT and NEVERUSEIT sides. Both sides seem to me to substitute easy-to-remember rules in place of actually thinking about the needs of the current task.

    -sff

    You're totally out of line. There's no pissing match when something gets its butt kicked 45 to 1. You don't need to use inflamatory terms like "religious fanatics" when good people have found an extreme performance problem. And if you're so proud of Expresso, you might want to provide a couple of your own performance tests.

    Thanks, Jeff. I was unsure what relevance the post had to a suggestion for a simple RegEx testing tool...

    The next bit isn't in any way argumentative, just illustrative...

    I'd add that the RegEx I use is on low row-count but high string-count-per-row data - data that's completely isolated to our custom app. Nasty stuff like pulling any and all of four possible custom operators and their parameters from a string pulled from XML built by the UI. Yuk but it works very well.

    e.g.

    using '\[\d+[\:\-*\d+]+\]' to shred:

    WHERE site_id = 81 AND ([3154:2]-[3154:1]=0 AND [3154:3]-[3154:2]=0 AND [3154:4]-[3154:3]=0 AND [3154:5]-[3154:4]=0 AND [3154:6]-[3154:5]=0 AND [3154:7]-[3154:6]=0 AND [3154:8]-[3154:7]=0 AND [3154:9]-[3154:8]=0)

    or 'DailySum\(\[\d+[\:\-*\d+]+\]\)' and '\[\d+[\:\-*\d+]+\]' to shred:

    WHERE site_id = 29 AND (DailySum([1116]) > 0 or DailySum([1048]) > 0 and [1117] > 0 or DailySum([1027]) > 0 or DailySum([1026]) > 0 or DailySum([1126]) > 0 or DailySum([1141]) > 0 or DailySum([1088]) > 0 or DailySum([1090]) > 0 and DailySum([1092]) > 0 or DailySum([1128]) > 0)

    Can't quite bring myself to make it go faster with custom T-SQL for the sake of a few updates per day.

    Another great "it depends" article and series of comments! (EXCEPT FOR THE MORONS POLLUTING THE SITE WITH THEIR CRASS ATTEMPTS AT ATTRACTING BUSINESS - THEIR ONLY SUCCESS: ATTRACTING VILIFICATION!)

    Gosh. Admittedly, I've spent no time learning Regex (just haven't needed it yet, I guess) and can only guess at what such parsing formulas do. That's why I was so happy that Craig posted some simple tests that I actually understand. I am definitely with you on not working on something for the sake of a few updates per day. There are much bigger fish to fry. But, as Solomon suggested, if I knew what these did, it might be fun to try to figure out a T-SQL way to do it.

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