• Dave62 (6/10/2014)


    SQLRNNR (6/10/2014)


    William Vach (6/10/2014)


    Question should have been "In SQL Server 2014, which of these is not a valid resource pool argument?".

    I'd probably go with setting. But the question is fine as is.

    According to the documentation, they are arguments that get values assigned to them. Maybe a setting could also be referred to as a value but not the argument itself.

    Didn't mean to split hairs, I just wanted to say something other than the standard "easy, thanks, ...". 😎

    And totally agree, the question is fine as.

    Thanks Steve!

    Well, I disagree with you and Jason. As the question is worded, it is obvious what the author thinks the answer is, but that doesn't make it a fine question, because when i create a resource pool I can call it pretty much what I like so all these could be valid resource polls, but none of these is either of teh built-in resource pools that come with reource governor so both "all of these" and "none of these" would be at least as correct as the "correct" answer and would actually answer the question that was actually asked (which is ambiguous anyway, hence two contradictory possible answers) rather than what Steve presumably intended to ask, which was what of teh listed things was not the name of a valid pool resource setting.

    Not a catastrophic error in the question, but if you've ever been involved in reviewing requirements statements to ensure that what development or production (as the case may be) understands them to mean is the same as what the people who raised the requirements intended the statement to mean you will know that this sort of misuse of terms is just not acceptable - or if you don't know that, I hope that you will enjoy trying to explain why a misunderstanding was allowed to go undetected when, at teh end of the day, the user acceptance trial rejects the thing because it works as development and QA thought it should but they thought wrong, as the inevitable result of not eliminating scope for misunderstanding at the start is discovering misunderstanding at the end.

    Tom