Microsoft Office Tutorials and References
In Depth Information
Database Versioning And Upgrade This provides a quick way to see the database versions
in use in case the content database is running an older version and should be upgraded.
Failover Server If you have SQL Server set up for failover services, the failover server
would be listed here.
Database Capacity Settings To prevent a database from growing too much and getting
out of hand, you can limit the number of site collections that are created in a single content
database. The default number is 15,000, but it can be set to whatever you like. There is also an
option to send out a notification if a certain number of site collections are reached. You
obviously want this to be lower than the actual limit, and the default is 9,000.
Note that on this page, the word site is used when describing the limit and warning level.
This is a misnomer; the settings apply to site collections, not to individual sites.
When the database hits its capacity, it will go Ofline—no new site collections will be permitted.
Search Server When you created the web application, you were prompted to choose a
search server for the content database. This setting is where you can change that choice if you
want to transfer the search process to another search server.
Remove Content Database Removing a content database from a web application does not
delete that database; it just disassociates it from the web application. The database still exists,
just as when you delete a web application and elect to not delete the content database. A
removed content database can be added to a web application later or used when you create a
new web application.
Preferred Server For Timer Jobs If you have multiple timer job servers, you can have the
content database use a preferred one. No Selection does not mean there is no timer job server;
it just means the content database has no preference and will use whatever server is available.
A D D I N G A N E W C O N T E N T D A T A B A S E
When the content database gets too large or hits its capacity limit, you may want to add a second
content database to the web application. In this case, additional site collections can be added
to the new database while still being part of the web application. A web application can have
numerous databases to accommodate increases in data storage.
To add a new content database, go to Central Administration’s Application Management
page, and click Manage Content Databases. Make sure you’re working with the web application
you intend to add the database to, and click the Add A Content Database . This will take you to
the Add Content Database page, as shown in Figure 10.82.
This page asks you to ill out the same information the content database required during
the creation of a new web application; in addition, it lets you specify the capacity site limit and
warning event level. Once you provide the needed information, click OK. You’ll see the new
content database listed on the Manage Content Databases page, as shown in Figure 10.83.
At this point, any new site collection created inside the web application will go to whichever
database has the most available space for site collections. The available space isn’t calculated by
storage capacity but by subtracting the existing number of sites in the database from the
database’s site limit.