SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Question of the Day for 06 Feb 2006


Question of the Day for 06 Feb 2006

Author
Message
Site Owners
Site Owners
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: Administrators
Points: 12703 Visits: 22
Comments posted to this topic are about the Question of the Day for 06 Feb 2006 posted at http://www.sqlservercentral.com/testcenter/qod.asp?QuestionID=700.
Yelena Varshal
Yelena Varshal
SSCrazy Eights
SSCrazy Eights (9.1K reputation)SSCrazy Eights (9.1K reputation)SSCrazy Eights (9.1K reputation)SSCrazy Eights (9.1K reputation)SSCrazy Eights (9.1K reputation)SSCrazy Eights (9.1K reputation)SSCrazy Eights (9.1K reputation)SSCrazy Eights (9.1K reputation)

Group: General Forum Members
Points: 9074 Visits: 600
I answered correctly, but the answers about the account not having Delete rights are valid too. Create Files / Write Data , Delete and Delete Subfolders and Files are 3 different advanced permissions for NTFS


Regards,
Yelena Varshal

Peter Kryszak
Peter Kryszak
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

Group: General Forum Members
Points: 1750 Visits: 3
I agree with your point that the "permissions options" are valid issues especially when best practices were mentioned.

I think the point of the question was that best practices, as implemented in the wizard, are not complete and require some additional steps to create a practical backup process.

--Peter



beezell
beezell
SSCrazy
SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)SSCrazy (2.2K reputation)

Group: General Forum Members
Points: 2216 Visits: 499
Bit late in the game, but trying to catch up. The question did mention they were setup with "best practices". Best practices would indicate that you would delete old backups...

Cheers,
Brian
Tom Thomson
Tom Thomson
One Orange Chip
One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)

Group: General Forum Members
Points: 26219 Visits: 12506
Peter Kryszak (2/6/2006)
I agree with your point that the "permissions options" are valid issues especially when best practices were mentioned.

I think the point of the question was that best practices, as implemented in the wizard, are not complete and require some additional steps to create a practical backup process.

--Peter


Maybe, but wouldn't best practises also include ensuring that permissions were correct, and ensuring that the requirement for these permissions was documented in such a way that future changes would take it into account?

Given that best practises clearly were no followed, I just went for the most obvious failure. I've had a junior person do that to one of my customers, and another do it to an in-house system; both were on Sql 2000 not on Sql 2005 but the principle is no different. I've never seen a disc filled by old backups through missing delete permissions. So it seems clear to me what the most obvious is, and I agree with the officially correct answer.

Tom

Primo Dang
Primo Dang
SSCrazy
SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)

Group: General Forum Members
Points: 2110 Visits: 1396
L' Eomot Inversé (8/1/2012)
Peter Kryszak (2/6/2006)
I agree with your point that the "permissions options" are valid issues especially when best practices were mentioned.

I think the point of the question was that best practices, as implemented in the wizard, are not complete and require some additional steps to create a practical backup process.

--Peter


Maybe, but wouldn't best practises also include ensuring that permissions were correct, and ensuring that the requirement for these permissions was documented in such a way that future changes would take it into account?

Given that best practises clearly were no followed, I just went for the most obvious failure. I've had a junior person do that to one of my customers, and another do it to an in-house system; both were on Sql 2000 not on Sql 2005 but the principle is no different. I've never seen a disc filled by old backups through missing delete permissions. So it seems clear to me what the most obvious is, and I agree with the officially correct answer.


To be fair, it only says best practises were used to build the maintenance plan, but not necessarily to set up the log backup.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search