March 2, 2017 at 10:40 pm
Comments posted to this topic are about the item SET PROCESS AFFINITY
March 2, 2017 at 10:42 pm
Nice, easy question to end the week on, thanks Steve
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
March 3, 2017 at 4:32 am
I gave the "correct" answer, but I think it is not correct. AUTO is not an option as far as I see, it is a value that you can use for the option CPU.
March 3, 2017 at 5:32 am
+1
According to MSDN, AUTO is an option for value of a featured syntax elements... 😉
Thanks Steve for this question.
March 3, 2017 at 6:54 am
Mighty - Friday, March 3, 2017 4:32 AMI gave the "correct" answer, but I think it is not correct. AUTO is not an option as far as I see, it is a value that you can use for the option CPU.
= AUTO 😉
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
March 3, 2017 at 3:52 pm
Henrico Bekker - Friday, March 3, 2017 6:54 AMMighty - Friday, March 3, 2017 4:32 AMI gave the "correct" answer, but I think it is not correct. AUTO is not an option as far as I see, it is a value that you can use for the option CPU.
= AUTO😉
:Whistling:
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
March 24, 2017 at 11:40 am
Although I got this right, I got it only by choosing the least wrong option. The "right" answer is horribly wrong.
If AUTO is an option, CPU isn't - the alternative to AUTO is a CPU-RANGE-SPEC not AUTO. AUTO and CPU-RANGE-SPEC are the two options for the CPU setting.
The NUMA option at the same level as AUTO is a NUMA-NODE-RANGE-SPAC, not NUMANODE, which is at the same level as CPU.
So if we want to say what are the three options rhan can be chosen at the end of the day we end up with AUTO, a CPU-RANGE-SPEC, and a NUMA-NODE-RANGE-SPEC as the three options and that's what the "right" answer should have said.
Of course one has the option of choosing either a CPU option or a NUMANODE option, so it would be correct (although rather pointless because it doesn't go far enough into our options) to say that we can specify either the CPU option or the NUMANODE option. but even that rather useless answer would have been closer to right than any of the options offered.
Tom
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply