Microsoft Office Tutorials and References
In Depth Information
Database Name and Authentication The web application needs a content database
to store everything in—just as the SharePoint-80 web application did during the initial
installation of SharePoint (as discussed in Chapter 3). You need to choose which SQL
Server instance you want the database to be stored on; of course, with a Standalone server
install, you’ll need to use the default provided as it points to the SQL Server Express
Database on the server. You can leave the database name as the default or rename it
something more intuitive if you want (the default creates a unique GUID for the database,
which is hard to remember). You’ll also need to decide how the web application will
authenticate to the database. Again, you’ll most likely want to use the default Windows
authentication, but if your SQL Server instance does not use Windows authentication, you’ll
need to supply a username and password.
13. Make certain that the correct database server is specified, the database name is
acceptable, and your web application can authenticate to access the database. My example uses
WSSBlog_Content for the database name; otherwise, the default database server and
authentication method are fine, as shown in Figure 10.27.
Failover Server If your SQL server is running database mirroring, you can specify the
failover server here.
14. Leave the failover server field blank if your SQL Server instance is not mirroring, which
mine isn’t. If your SQL Server instance is doing database mirroring, feel free to enter that
server name here.
Search Server For the search service to index the content database for this new web
application, a search server must be assigned. The drop-down list shows only those servers
running the Windows SharePoint Services search service.