January 11, 2007 at 7:09 am
(bit) should be (not), but I can't edit the subject anymore 😉
Hi,
I'm kind of new to ms sql, so I hope you forgive me for my ignorance:
My hosting provider doesn't grant db_owner access to my hosted ms sql server database account. According to them the db_owner has some undesirable permissions, such as for instance increasing it's own allowed database size and giving more (processing) priority in to it's own database over other databases, which are undesirable in a shared hosting scenario.
Although I wouldn't dare to question them, I'd like to get a second opinion from someone with more experience on this than me, since I've seen other hosting providers do offer db_owner access in shared hosting scenarios.
I was hoping someone could give me arguments why db_owner access in shared hosting is possible without potentially "harming" other databases that I can use to try to persuade/prove db_owner access is harmless.
If not, am very interested in the exact why not.
Does the same also apply for ms sql express?
Thanks in advance,
Rutger
January 11, 2007 at 8:26 am
i don't manage a hosted db, but i can understand it. you are signing a contract and they charge you based on their calculations of the resources you will use.
if they allowed everyone to increase the amount of resources devoted to their instance then it would impact everyone else. another reason may be for backups. dbo can change permissions and i've seen permissions changed on nt files accidentaly and the backup fails. in their case they may not notice and it opens up the possibility of data loss
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply