Re: Complete Neophyte Question(s)
- From: "bass_player [SBS-MVP]" <bass_player@xxxxxxxx>
- Date: Sat, 30 Jun 2007 04:48:38 +0800
I'd recommend that you go for a training course ;-)
"James" <minorkeys@xxxxxxxxx> wrote in message
news:eVtdKXmuHHA.1168@xxxxxxxxxxxxxxxxxxxxxxx
I have inherited a SQL Server (2005) from an outgoing DBA and while I'm
familiar with databases from a data structure/manipulation standpoint, the
permissions/security model in SQL Server 2005 has baffled me thus far. I
digress...
As far as I can tell, our previous DBA create a role which is called
SP_Exec. I know that this role has permissions defined somehow, but I'll
be damned if I can figure it out. One of our users can modify a
particular view, and another can't. The only difference I can see is that
one is a member of this role and the other isn't. If I remove the role
from the user who CAN modify the view, he no longer can. Alas, I have no
idea where this is defined.
Schemas are also slightly confusing, but I imagine that's just a way of
logically grouping sets of objects. At first glance it seems everything
is utilizing the a schema called dbo. One of our users was having trouble
until I went into the schema and added "View Definition" as a permission.
I'm not even certain what this effectively did, but it solved the problem
while I try to figure out how this whole thing works.
Can anyone point me in the direction of a document that explains this in
English? Perhaps the majority of my hang-ups are with Management Studio
and not the actual structure of the overall permissions model. ANY help
would be appreciated.
.
- References:
- Complete Neophyte Question(s)
- From: James
- Complete Neophyte Question(s)
- Prev by Date: Re: SQL account password not valid after rebuild
- Next by Date: Re: Complete Neophyte Question(s)
- Previous by thread: Complete Neophyte Question(s)
- Next by thread: Re: Complete Neophyte Question(s)
- Index(es):