SET Options - 1

  • Comments posted to this topic are about the item SET Options - 1

    If everything seems to be going well, you have obviously overlooked something.


    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • Another Great question Ron!

    I was not aware of this limitation and got the question wrong 🙂

    ~ Lokesh Vij

    Guidelines for quicker answers on T-SQL question[/url]
    Guidelines for answers on Performance questions

    Link to my Blog Post -->[/url]

    Follow me @Twitter

  • Great question to end the week. Had to do some research, but it was worth it.

    Need an answer? No, you need a question
    My blog at
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • This was removed by the editor as SPAM

  • Good question Ron.


    -------------------------------Posting Data Etiquette - Jeff Moden [/url]Smart way to ask a question
    There are naive questions, tedious questions, ill-phrased questions, questions put after inadequate self-criticism. But every question is a cry to understand (the world). There is no such thing as a dumb question. ― Carl Sagan
    I would never join a club that would allow me as a member - Groucho Marx

  • Nice question, thanks.

  • Really nice question. I even did the research on each option, but somehow missed the line about indexed views. Looks like I need to brush up on my options!

    (And I will smack the first guy who says "Thanks for the easy question to end the week!") 😉


    a haiku...

    NULL is not zero
    NULL is not an empty string
    NULL is the unknown

  • Great question to end the week! Thanks.

  • Thanks for the easy question to end the week!


  • Great question.

    But, okay... I give up, how does having an indexed view cause a loss of precision?

    (I.e. Yep, I see the error. I don't understand WHY. 🙁 )

  • Great Question...

    many thanks

  • Good question Ron.

    Clear answer and the SQL statements did not distract from the truth you where creating.


  • Thanks for the great question Ron. I was unaware of this limitation and have definitely learned something today. 🙂

    Everything is awesome!

  • I've been looking for Steve Moden's phone number, thanks....

    How best to post your question[/url]
    How to post performance problems[/url]
    Tally Table:What it is and how it replaces a loop[/url]

    "stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."

  • Rich Weissler (12/14/2012)

    Great question.

    But, okay... I give up, how does having an indexed view cause a loss of precision?

    (I.e. Yep, I see the error. I don't understand WHY. 🙁 )

    It doesn't. But there are specific settings required for making and maintaining indexed views, and this happens to be one of them.

    If you change the setting before trying to create the view, that in itself would already fail. (Or, to be more precise, creating the view would succeed, but creating the index to convert it from a normal into an indexed view would fail).

    The reason for this limitation? (Puts on speculative hat) Many settings are discouraged anyway, and I guess that MS decided not to put in extra engineering effort to support and test indexed views (and several other features with similar limitations) under all those settings. So they simply forbid them.

    Hugo Kornelis, SQL Server/Data Platform MVP (2006-2016)
    Visit my SQL Server blog:
    SQL Server Execution Plan Reference:

Viewing 15 posts - 1 through 15 (of 32 total)

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