June 7, 2017 at 10:29 pm
Comments posted to this topic are about the item DBCC SQLPREF
“When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris
June 7, 2017 at 10:30 pm
The correct answer is NONE OF THE ABOVE
There is no DBCC SQLPREF command.
June 7, 2017 at 11:16 pm
I presume you meant DBCC SQLPERF
and not SQLPREF (which is not a DBCC option)
Other than the obvious typo, nice question.
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
June 8, 2017 at 1:36 am
Stewart "Arturius" Campbell - Wednesday, June 7, 2017 11:16 PMI presume you meantDBCC SQLPERF
and not SQLPREF (which is not a DBCC option)
Other than the obvious typo, nice question.
And, assuming that the typo is corrected, the answer is still NONE OF THE ABOVE, because DBCC SQLPERF, as written in the question, gives an error message
What checks space in the log is DBCC SQLPERF(LogSpace), and the DBCC statement can do several other things, depending on parameters passed to it, some documented, some not.
The question is like asking "What session does KILL terminate?" with answers of 1, 0, 75 and 56452322
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 8, 2017 at 2:27 am
Great trolling question there!
June 8, 2017 at 3:53 am
My train of thought on seeing this went domething like this... SQLPREF? Something odd there. Isn't it meant to be SQLPERF? Never actually used it, being more a developer than a DBA, so let's look at BOL... Hah! Trick question! Hmm - the only safe course of action is to think like a computer, (if it can be called thinking). The answer is obviously "syntax error" or similar... Let's see what the multi-choice answers are.. oh! Syntax errors not on the list! Must be a typo, albeit a repeated one. Let's try DBCC SQLPERF then... Hmm - parameter missing! I really want to post a comment, but I can't unless I answer the question. Temporarily suspending my computer-like thinking, I deduce that the closest answer is the last one, and lo and behold, it awards me a point!
To be honest, I really feel as if I cheated. Steve, feel free to deduct that point.
Top marks for entertainment value though, even if that was accidental! It all goes to show how hard it can be to think like a computer!
MarkD
June 8, 2017 at 5:17 am
What's amazing to me is the typo is in the subject of the question as well as the question itself.
June 8, 2017 at 7:57 am
And of course the "correct" answer is only half correct anyway as SQLPERF can also reset wait and latch statistics.
_______________________________________________________________
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/
June 8, 2017 at 8:04 am
Is it required to be accurate in typing to be DBA? That's the question.
June 8, 2017 at 8:46 am
Assuming we use DBCC SQLPERF with the parameter LOGSPACE the explanation is wrong.
"Check the amount of space available in a transaction log file."
BOL says the opposite "amount of space used" and not "the amount of space available".
From BOL:
LOGSPACE
Returns the current size of the transaction log and the percentage of log space used for each database. You can use this information to monitor the amount of space used in a transaction log.
June 20, 2017 at 7:48 am
Again 'typos' in the question (and the answer). Sometimes the 'typo' is there deliberately. So when do we know when this is the case and when not?
August 16, 2017 at 10:40 pm
GilaMonster - Thursday, June 8, 2017 1:36 AMStewart "Arturius" Campbell - Wednesday, June 7, 2017 11:16 PMI presume you meantDBCC SQLPERF
and not SQLPREF (which is not a DBCC option)
Other than the obvious typo, nice question.And, assuming that the typo is corrected, the answer is still NONE OF THE ABOVE, because DBCC SQLPERF, as written in the question, gives an error message
What checks space in the log is DBCC SQLPERF(LogSpace), and the DBCC statement can do several other things, depending on parameters passed to it, some documented, some not.
The question is like asking "What session does KILL terminate?" with answers of 1, 0, 75 and 56452322
Just getting around to this question and I could not decipher a correct answer from the list of answers. I really do not like this question as currently constructed.
I am glad Gail brought up the issues with this question because I would do the same in this case.
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
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply