Post reply

When NULL IS NOT NULL

  • July 30, 2013 at 6:22 pm

    #1637180

    Just wanted you all to know I appreciate the research you've done and I haven't absconded from this thread. Merely lurking until I have something of value to add.

    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    My thought question: Have you ever been told that your query runs too fast?

    My advice:
    INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
    The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.

    Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
    Since random numbers are too important to be left to chance, let's generate some![/url]
    Learn to understand recursive CTEs by example.[/url]
    [url url=http://www.sqlservercentral.com/articles/St

  • July 31, 2013 at 3:41 am

    #1637284

    I agree with ChrisM@Work, that there is nothing in the query plan explaining such extravagant behaviour of these queries.

    From what I can see, it's only happens when you UNION ALL between results of some nondeterministic functions.

    I would call it bug, but MS most likely will call it "SQL optimizer feature"

    😉

    _____________________________________________
    "The only true wisdom is in knowing you know nothing"
    "O skol'ko nam otkrytiy chudnyh prevnosit microsofta duh!":-D
    (So many miracle inventions provided by MS to us...)

    How to post your question to get the best and quick help[/url]

Viewing 2 posts - 16 through 18 (of 18 total)

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