Microsoft Office Tutorials and References
In Depth Information
FIGURE 3.54
SharePoint’s
databases on the
SQL server
It helps to know what accounts have been assigned access to the databases. If you remember,
originally only the setup account had roles set up on the SQL server. But when configuration
began, the setup account added the farm account to the SQL server’s login roles, as well as the
DBCreator and SecurityAdmin roles. This let the setup account step away from managing SQL
for SharePoint any longer and let the farm account do it.
To this end, the configuration database for SharePoint was created by the setup account, but
the farm account was given ownership of it after. From that point on, the farm account is the
dbo (static database owner role) for all SharePoint databases, but it may assign other SharePoint
accounts access to those databases depending on what they require.
To check to see what the users are for the configuration database, take the following steps
(you can use the same method on all databases):
1. Select the database (in my case, SharePoint_Conig, which you might remember was the
default name for it during configuration, which I kept) in the Object Explorer pane.
2. In the details pane, open the Security folder, and then open Users.
As you can see in Figure 3.55, all accounts that might need to be able to read (or change)
the configuration database have been added. Of specific note is that the farm account is
there (in my case, dem0tek\spffarm), and the setup account isn’t.
That’s because the setup account is the static dbo for the database. It created the
configuration database during installation and then handed off ownership of it to the farm
account later.
3. To prove that (and find the setup account), double-click dbo in the details pane.
Search JabSto ::




Custom Search