January 23, 2012 at 3:40 am
Sometimes when you get the answer wrong, you just know what the conversation will be here.
...and rightly so, the question is setup wrong, but not deliberately so give Steve a break and its not exactly life or even business critical.
Still... I want my point back!! 😛
_____________________________________________________________________
[font="Comic Sans MS"]"The difficult tasks we do immediately, the impossible takes a little longer"[/font]
January 23, 2012 at 3:51 am
Hello,
I think there is something wrong, The correct Answer is A and D.
!
.
January 23, 2012 at 4:03 am
Good question Steve, but answer its wrong!!!
A and D it's correct!!!!
the resource governor doesn't limit I/O, but limits CPU and Memory utilization!!!
January 23, 2012 at 5:39 am
Good question and I never thought of using Resource Governor for backups, but I agree the answers should be A & D since the explanation deals with CPU in resource governor rather than I/O.
January 23, 2012 at 5:39 am
neprosto (1/23/2012)
wrong answer A & C !When we enable compression we increase the cpu load and decrease the io load as we need less space for saving beckup. So we must use Resource Governor with limited cpu resource pool.
Right answer are A & D.
PS Give me back my point !:-D
+1
January 23, 2012 at 6:17 am
I agree -- looks like the answers should enable compression and limit the CPU
January 23, 2012 at 7:01 am
Didn't we had a long discussion months back that "IF ther are 2 or more than 2 options"
The questiopn should mention that??
Regards,
Skybvi
Regards
Sushant Kumar
MCTS,MCP
January 23, 2012 at 7:03 am
Good question but wrong answer. And even if the answer had said A and D it would still have been somewhat wrong, since creating a user doesn't give that user permission to do backups and doesn't change your backup jobs to run under that user either, and if you don't do those additional things D is irrelevant.
Tom
January 23, 2012 at 7:06 am
I too must jump in and ask for the question to be corrected 🙂
Having implemented Resource Governor, I opened up a workload Group, because for the life of me I only remembered resources involving memory and CPU, not I/O. And I was 99% certain that the backup command didn't have that option.
Then I was wrong.... and the answer said I should have been right.
Steve make sad Panda.
January 23, 2012 at 7:07 am
Points have been awarded back and the answers corrected. The wrong one was selected.
My apologies.
January 23, 2012 at 7:08 am
And it seems that Steve has corrected the question 🙂
Steve make Happy Panda now!
January 23, 2012 at 7:12 am
mtassin (1/23/2012)
Steve make Happy Panda now!
Like this? 😀
January 23, 2012 at 7:20 am
Steve Jones - SSC Editor (1/23/2012)
Points have been awarded back and the answers corrected. The wrong one was selected.My apologies.
Thank you Steve, Good way to start the week, with some bonus points 🙂
M&M
January 23, 2012 at 7:47 am
A really good question anyway. Thank you, Steve.
I never thought about using Resource Governor to limit CPU on a database backup.
Sometimes making a backup will eat almost 100% CPU and it's a good think to know how to deal with that.
Best regards,
Andre Guerreiro Neto
Database Analyst
http://www.softplan.com.br
MCITPx1/MCTSx2/MCSE/MCSA
January 23, 2012 at 7:48 am
Good question, thank you.
Iulian
Viewing 15 posts - 16 through 30 (of 43 total)
You must be logged in to reply to this topic. Login to reply