Are the posted questions getting worse?

  • jasona.work (9/19/2016)


    Brandie Tarvin (9/19/2016)


    jasona.work (9/19/2016)


    I may be just a duck, but I'm an EEVVIILL little duck!

    :hehe:

    It's DUCK HUNTING SEASON!

    EDIT: Added URL

    WABBIT SEASON!

    I've been in those meetings.....:-D

    😎

  • More like "people" season. Some people just don't get it. See the following where what someone is doing actually could kill people. I've confirmed Sergiy's findings with the given test data.

    http://www.sqlservercentral.com/Forums/Topic1818451-3077-1.aspx

    Medical profession and system is going to hell in a handbasket. I remember being in the hospital for my heart and they took my blood pressure. It was 90 over 60. The nurse handed me a cupful of pills and so I asked what they were. Two of the pills were to lower my blood pressure. I'd probably have died if I'd taken them. :Whistling:

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

  • Brandie Tarvin (9/19/2016)


    Eirikur Eiriksson (9/19/2016)


    Hi all,

    I'm writing few pieces on XML operation's performance in SQL Server, both generating the XML, parsing it and operations on it and I'm wondering if anyone has any particularly complex examples or problems to share?

    😎

    We use the XML data type to store history for a few critical tables. There are triggers on the tables that fire when an update is done, copying the data over to a logging table that has 3 columns. An id column for the table, the trigger datetime, and the XML data type which contains all the source table's columns for the updated record.

    We do this because our users come back to us complaining that data mysteriously got changed and none of them did it, so the system has to be messed up. At which point, we have to query those log tables and find the record in question, the tell the users exactly who did the update (because yes, that gets logged as part of the table information). This has actually stopped the IT Screwed It Up! blame game since we can now point to the exact user who did the dirty deed. Sometimes it's just someone who needs training on proper updates. Mostly it's a user trying to throw us under the bus for a bad decision they don't remember.

    Does this help you with your article?

    Thank you for this Brandie, it does help as it reminded me of a body of work I did on auditing in high volume systems where only the XML auditing methods performed fast and efficiently enough to not hamper the overall performance.

    😎

  • Interesting on both. I'd love to see the trigger code for those.

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

  • Eirikur Eiriksson (9/19/2016)


    Hi all,

    I'm writing few pieces on XML operation's performance in SQL Server, both generating the XML, parsing it and operations on it and I'm wondering if anyone has any particularly complex examples or problems to share?

    😎

    Heh... when you want to go fishing, go where the fishing is good. Think about the XML stored in cached plans. The cool part is that every one has those and, like me, has a need to be able to parse parts out... especially when undocumented Trace Flag 8666 has been activated to provide "extra parts". 😀

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

  • Jeff Moden (9/19/2016)


    More like "people" season. Some people just don't get it. See the following where what someone is doing actually could kill people. I've confirmed Sergiy's findings with the given test data.

    http://www.sqlservercentral.com/Forums/Topic1818451-3077-1.aspx

    Medical profession and system is going to hell in a handbasket. I remember being in the hospital for my heart and they took my blood pressure. It was 90 over 60. The nurse handed me a cupful of pills and so I asked what they were. Two of the pills were to lower my blood pressure. I'd probably have died if I'd taken them. :Whistling:

    I have to wonder how many flawed systems such as the one in that post, are out there "in the wild." Especially with the rush for practices to get on EHRs / EMRs about 3-4 years ago (practices, if I recall, would get a payment from the Gov if they went to an EHR and got certified in a fairly short amount of time, which led to a rush of companies pushing out EHR systems.) So, you had companies either "whipping up" something in a very short time, shoehorning features to qualify into an existing product, or jumping into using back-end software they had little or no experience with.

    There's two industries that really, really need to be as close to bullet-proof as possible with their systems:

    1. Drs / hospitals

    2. Self-driving cars

    Can you imagine what would end up on the roads if the NHTSA announced incentives for companies who could show "meaningful use" of self-driving cars / trucks? You'd have companies home-brewing bolt-on kits to "drive" these things (using what pretty much happened with the EHR incentives) with almost no testing...

  • Jeff Moden (9/19/2016)


    Eirikur Eiriksson (9/19/2016)


    Hi all,

    I'm writing few pieces on XML operation's performance in SQL Server, both generating the XML, parsing it and operations on it and I'm wondering if anyone has any particularly complex examples or problems to share?

    😎

    Heh... when you want to go fishing, go where the fishing is good. Think about the XML stored in cached plans. The cool part is that every one has those and, like me, has a need to be able to parse parts out... especially when undocumented Trace Flag 8666 has been activated to provide "extra parts". 😀

    Thanks Jeff, I like the idea.

    😎

  • I'm normally very tolerant when it comes to noobs but this one only leaves me three choises

    😎

    1) deaf

    2) daft

    3) dumb

  • Eirikur Eiriksson (9/19/2016)


    I'm normally very tolerant when it comes to noobs but this one only leaves me three choises

    😎

    1) deaf

    2) daft

    3) dumb

    I think that is only two choices as daft and dumb are basically the same thing. 😉

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • Sean Lange (9/19/2016)


    Eirikur Eiriksson (9/19/2016)


    I'm normally very tolerant when it comes to noobs but this one only leaves me three choises

    😎

    1) deaf

    2) daft

    3) dumb

    I think that is only two choices as daft and dumb are basically the same thing. 😉

    That's down to my broken English 🙂

    😎

  • Sean Lange (9/19/2016)


    Eirikur Eiriksson (9/19/2016)


    I'm normally very tolerant when it comes to noobs but this one only leaves me three choises

    😎

    1) deaf

    2) daft

    3) dumb

    I think that is only two choices as daft and dumb are basically the same thing. 😉

    Few more options here but the problem is still the same

    😎

    SELECT

    PST.PROPERTY_VALUE

    FROM POSTERS.PROPERTIES PST

    WHERE PST.ANNOYING = 1

    absurd

    airheaded

    asinine

    balmy

    barmy

    bats

    batty

    bedlam

    birdbrained

    bonkers

    boobish

    brain-dead

    brainless

    brainsick

    bubbleheaded

    buffoonish

    bughouse

    certifiable

    chowderheaded

    chuckleheaded

    clownish

    clueless

    cockeyed

    crackbrained

    cracked

    crackers

    crackpot

    cranky

    crazed

    crazy

    cuckoo

    daffy

    demented

    dense

    deranged

    dim

    dim-witted

    dippy

    doltish

    dopey

    dorky

    dotty

    dull

    dumb

    dunderheaded

    empty-headed

    fallacious

    farcical

    fatuous

    featherheaded

    feebleminded

    fey

    fool

    foolish

    fruity

    gaga

    gormless

    half-baked

    half-witted

    harebrained

    haywire

    idiotic

    ill-advised

    illogical

    imbecile

    inept

    insane

    invalid

    irrational

    jerky

    knuckleheaded

    kookie

    kooky

    lamebrain

    laughable

    loco

    looney

    loony

    loony tunes

    loopy

    ludicrous

    lunkheaded

    mental

    meshuggah

    meshugge

    mindless

    moonstruck

    moronic

    non compos mentis

    nonrational

    nonsensical

    notional

    nuts

    nutty

    oafish

    obtuse

    off

    opaque

    pinheaded

    potty

    preposterous

    psycho

    psychotic

    ridiculous

    sappy

    scatty

    screwball

    screwy

    senseless

    silly

    simple

    simpleminded

    slow

    slow-witted

    soft

    softheaded

    stupid

    surd

    teched

    thick

    thickheaded

    thoughtless

    tomfool

    touched

    unbalanced

    unconsidered

    unhinged

    unintelligent

    unreasonable

    unreasoned

    unreasoning

    unsound

    unwise

    vacuous

    wacko

    wacky

    weak

    weak-minded

    whacko

    whacky

    witless

    wud

    zany

  • Eirikur Eiriksson (9/19/2016)


    Sean Lange (9/19/2016)


    Eirikur Eiriksson (9/19/2016)


    I'm normally very tolerant when it comes to noobs but this one only leaves me three choises

    😎

    1) deaf

    2) daft

    3) dumb

    I think that is only two choices as daft and dumb are basically the same thing. 😉

    That's down to my broken English 🙂

    😎

    Maybe 1) deaf 2) dumb 3) crazy would be a better collection. But even then you wouldn't have three choices, since looking at the OP's performance in that thread makes it clear that your only reasonable option is "all three".

    Tom

  • Eirikur Eiriksson (9/19/2016)


    Sean Lange (9/19/2016)


    Eirikur Eiriksson (9/19/2016)


    I'm normally very tolerant when it comes to noobs but this one only leaves me three choises

    😎

    1) deaf

    2) daft

    3) dumb

    I think that is only two choices as daft and dumb are basically the same thing. 😉

    Few more options here but the problem is still the same

    😎

    SELECT

    PST.PROPERTY_VALUE

    FROM POSTERS.PROPERTIES PST

    WHERE PST.ANNOYING = 1

    absurd

    airheaded

    asinine

    balmy

    barmy

    bats

    batty

    bedlam

    birdbrained

    bonkers

    boobish

    brain-dead

    brainless

    brainsick

    bubbleheaded

    buffoonish

    bughouse

    certifiable

    chowderheaded

    chuckleheaded

    clownish

    clueless

    cockeyed

    crackbrained

    cracked

    crackers

    crackpot

    cranky

    crazed

    crazy

    cuckoo

    daffy

    demented

    dense

    deranged

    dim

    dim-witted

    dippy

    doltish

    dopey

    dorky

    dotty

    dull

    dumb

    dunderheaded

    empty-headed

    fallacious

    farcical

    fatuous

    featherheaded

    feebleminded

    fey

    fool

    foolish

    fruity

    gaga

    gormless

    half-baked

    half-witted

    harebrained

    haywire

    idiotic

    ill-advised

    illogical

    imbecile

    inept

    insane

    invalid

    irrational

    jerky

    knuckleheaded

    kookie

    kooky

    lamebrain

    laughable

    loco

    looney

    loony

    loony tunes

    loopy

    ludicrous

    lunkheaded

    mental

    meshuggah

    meshugge

    mindless

    moonstruck

    moronic

    non compos mentis

    nonrational

    nonsensical

    notional

    nuts

    nutty

    oafish

    obtuse

    off

    opaque

    pinheaded

    potty

    preposterous

    psycho

    psychotic

    ridiculous

    sappy

    scatty

    screwball

    screwy

    senseless

    silly

    simple

    simpleminded

    slow

    slow-witted

    soft

    softheaded

    stupid

    surd

    teched

    thick

    thickheaded

    thoughtless

    tomfool

    touched

    unbalanced

    unconsidered

    unhinged

    unintelligent

    unreasonable

    unreasoned

    unreasoning

    unsound

    unwise

    vacuous

    wacko

    wacky

    weak

    weak-minded

    whacko

    whacky

    witless

    wud

    zany

    You've forgotten the "Modenism" that encompasses all of those... "Moroff". This is a person that doesn't even merit being called a "Moron" because they're more off than on. 😛

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

  • Jeff Moden (9/19/2016)


    You've forgotten the "Modenism" that encompasses all of those... "Moroff". This is a person that doesn't even merit being called a "Moron" because they're more off than on. 😛

    Wow! You know me Jeff and we haven't even met :w00t:

    Far away is close at hand in the images of elsewhere.
    Anon.

  • Sad to see spam is still an issue here.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

Viewing 15 posts - 55,876 through 55,890 (of 66,712 total)

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