Microsoft Office Tutorials and References
In Depth Information
WSS_Search_( servername ) This is the database created by SharePoint to be used by the
Search service. The data collected by Search’s indexing service is first stored locally on the
server that runs the service, but for the long run, that information gets shipped to the Search
database. So when someone queries a site, Search looks first in the database for the results, in
the change logs for the content databases, and then in the index files stored in the SharePoint
root on the server for recent changes.
Although SQL Express doesn’t have any robust, built-in backup features, you can use the
file system backup utility to back up these databases in case of emergency. This makes it even
more important that you know where the database files (and their logs) are located and which
ones relate to what part of SharePoint. See Chapter 13, “Maintenance and Monitoring,” for more
information about disaster recovery. In addition, you can install the SQL Management Studio
Express to manually back up and restore the SQL Server Express databases. Chapter 15 also
details how to install the SQL Management Studio for SQL Server Express.
Now that we’re done looking at the SharePoint root and the SharePoint databases, feel free to
close the Explorer windows.
Confirming the Services and Their Accounts
SharePoint requires many of its services to interact directly with services and resources running
on the server. This means that these services must have an account identity to make requests. (It
also means that those accounts must be able to log in as a service; keep that in mind if your
environment uses group policies to disallow such login, because exceptions might have to be made.)
When SharePoint is installed using the Standalone method, all services are configured
automatically using local system accounts. This is why everything is up and running as soon as you
finish the configuration wizard.
But to make sure of what services were installed, which ones are running, and which
accounts they’re using, you’ll need to take a look at the Services console.
T here are several ways to open the Ser v ices console. You can select it in the Ser ver Manager console,
under Configuration in the navigation pane; you can click the Services button on the Services tab
in the Task Manager (my usual method, because I always have the Task Manager open to track CPU
and RAM usage in real time); and, of course, you can go to Start Administrative Tools Services
or use the search field in the Start menu to find it.
To do that, open the Services console (Start menu Administrative Tools Services). The
services we are looking for start with either SQL or SharePoint .
As you scroll down the console (if it is sorted by service name), the first services related to the
SharePoint installation that you’ll come across should be the six SharePoint services: SharePoint
2010 Administration, Timer, Tracing, User Code Host, VSS Writer services, as well as the SharePoint
Foundation Search V4 service. Not all of these services need to be running; some, like the VSS
Writer service, stop and start when needed (the Timer service is an exception; it must be Started,
meaning running, in order for SharePoint to work). Each one of the services has a short description
in the Description field if you’d like to know more about them. Most importantly, the console
indicates which services are running and which account they are using as their identity.
Search JabSto ::

Custom Search