• kevin.l.williams (3/24/2011)


    rmechaber (3/24/2011)


    Sean Lange (3/24/2011)


    rmechaber (3/24/2011)


    As others have pointed out, the "correct" answer is wrong. Powershell is NOT an option in 2005. I got it right for the wrong reason: I guessed that Powershell integration was more likely in in 2008 than an RS subscription.

    These kinds of versioning problems with QoD are common enough and easily prevented: couldn't SSC require all submitters to specify which versions they have tested their question on?

    Rich

    By that same logic it is also correct if the version is 2008. With no version specified it could be right OR wrong. You feel it is wrong because you are on 2005 and the author feels it is right because he is on 2008.

    I would definitely say that the QOTD lived up to its expectations in that it made you think and learn something. Version challenges will always be an issue with QOTD because we get cool new features with each new version and there are always going to be people that are not on the most current version.

    Sean, I will respectfully disagree: if it's not always true, then it's false.

    There is no reason for these ambiguities to exist and persist in QoD, when it's easy enough for submitters to check the questions beforehand, either on their own systems or, if necessary to cover other versions, someone else's. At the very least, if the question were only marked as "Tested on SQL Server 2008 R2," we'd know that much.

    I don't care about getting points or the number of right answers I get. I care about misinformation propagated as truth. It is misleading and incorrect to identify a "correct" answer without qualifying the circumstances under which the answer is, in fact, correct.

    Rich

    This type of issue has sparked some heated exchanges in recent QoDs. I second the request that all questions contain something like this "Tested on default install SQL Server XXXX, language: us_english".

    Kevin

    I absolutely agree that version should be mentioned with every question. One of the biggest challenges is that we don't all have all the versions available to us. The version argument will continue until the end of time and as you suggested the best (and probably only) way to avoid it is to have the version number(s) as part of the question.

    _______________________________________________________________

    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/