Microsoft Office Tutorials and References
In Depth Information
FIGURE 2.38
The WSS_WPG in
the Conig folder
permissions
These security groups and their members are not really important for a Standalone
installation, because all of the accounts used by SharePoint are local to the computer. However,
these groups and where their permissions are applied can be useful should you want to make
changes to the accounts used by SharePoint or you need to troubleshoot permissions. They are
also very important to know during the Complete installation, because most accounts, in that
context, will be domain users and not local.
SQL HAS GROUPS, TOO
You might have noticed in Figure 2.37 that there are also a number of groups on the server for the
SQL ser v ices to manage the local installation of SQL Express. T hese groups w ill not be available for
SharePoint installations that don’t also have some version of SQL installed locally.
Confirming the Installation of Databases
Now that you know that SharePoint’s root folders are there, let’s see about the databases. During
the prerequisite installation phase, you got a glimpse of the folder SQL Server 2008 Express used.
If you go back there now (conveniently buried deeply in the SharePoint root at %Program Files%\
Common Files\Microsoft Shared\Web Server Extensions\14\Data\MSSQL10.SHAREPOINT\
MSSQL\DATA), you can see in Figure 2.39 that there are more than just the requisite SQL databases
(such as Model and Master). Now there are a number of new databases (and their logs) in existence,
and each is used by SharePoint:
Bdc_Service_DB_( GUID ) This is automatically generated for use by the new Business
Data Connectivity capabilities available to SharePoint Foundation.
SharePoint_AdminContent_( GUID ) Since Central Administration has its own website
on a separate (custom, randomly generated) port from the default website, it requires its
own web application. Each web application gets its own database. Thus, this is Central
 
Search JabSto ::




Custom Search