January 13, 2006 at 2:00 am
Hi, I am a developer that is having a problem with a sql database in a shared hosting environment. My provider has recently limited my user's permission set. Now, my user's permission set does NOT include the DBO, for my databases. This is a huge problem.
Tools, like the DTS import, don't function correctly anymore (meaning alot of the data transfers, but critical underlying things like relationships, indexes and primary keys don't transfer -- with permission errors).
I'm sure there are workarounds, but could you help me outline the techincal reasons why they should be unafraid to give me DBO access to my own Dbs? They are basing their policy off of default settings from a hosting management tool that they are using.
Thank you.
Bryan
January 13, 2006 at 11:49 am
Bryan -
With the assumption that this is an internet hosting provider, not a corporate or other environment where restrictions might be mandated by SOX or other mandate, you have every right to expect DBO priviledges in your own databases. You're paying for a service, not to be hassled by the provider, worst case you may have to "vote with your feet" and find another provider.
On the other hand, your provider may well have provided DBO access in your own databases but not sysadmin/DBO on the server in which case you just need to work differently (e.g. all scripts, etc. need to specify that the object owner should be DBO rather than your user ID). I don't know how many times I've had users say "I can't do this anymore" because of the differences between having server wide DBO access vs. database specific permissions.
Joe
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply