Datasheet

EXCHANGE SERVER ARCHITECTURE 19
Maximum Number of Databases and Database Availability Groups
Exchange Server 2010 Standard Edition permits a maximum of five mailbox databases on each
Mailbox server. Exchange Server 2010 Enterprise Edition permits a maximum of 100 mailbox
databases per Mailbox server. The maximum number of mailbox databases includes both the
active and the passive copies. You must take this into consideration when planning database
availability groups.
Smaller Transaction Logs
Experienced Exchange 2000/2003 administrators will immediately recognize an Exchange trans-
action log because they are always 5,120 KB in size. Exchange 2010 transaction logs, however,
are a bit smaller. In fact, the transaction log files are quite a bit smaller — 1,024 KB to be exact.
The transaction log files are smaller because Exchange 2010 includes continuous replication,
which allows log files to be copied to another location and replayed into a backup copy of their
corresponding database. Reducing the log file sizes ensures that data is copied more quickly to
the target.
Improved Search Features
Content indexing has been completely rewritten in Exchange 2010 so that it is far more efficient
than in previous versions and is more closely integrated with the Information Store service.
Improvements have been made so that the indexing process is throttled back during peak loads
and does not affect client use of the Exchange server. By default, each mailbox database auto-
matically has a full-text index associated with it. Messages are indexed upon arrival rather than
on a fixed schedule; the index is up-to-date and immediately available to clients.
Full-text search capabilities are available from both Outlook clients as well as Outlook Web
App and Windows Mobile devices. Searches can be done by word, phrase, or sentence, and
in addition to the message bodies, attachments such as Word documents, Excel spreadsheets,
text files, and HTML files can be searched. Where previously the content index could consume
between 20 and 40 percent of the size of the database, Exchange Server 2010 content indexing
(enabled by default) usually consumes between 5 and 10 percent of the total size of the mailbox
database.
Exchange Server Management
Server management with Exchange 2010 becomes increasingly complex as administrators try to
make Exchange work within their o rganizations, particularly in larger organizations. Exchange
2000/2003 management of mail recipients was performed through the Active Directory Users
and Computers console, while management of Exchange Server–related tasks and global recip-
ient tasks is performed through the Exchange System Manager console. In Exchange 2010, all
recipient administration tasks are now performed through the Exchange Management Console
(EMC) or the EMS.
With previous versions of Exchange Server, such as 5.5, 2000, or 2003, medium-sized and
large organizations often had specific needs to perform bulk changes to Exchange data, manage
Exchange servers from the command line or scripts, and access or manipulate data stored
in Exchange databases. Although making bulk changes or manipulating Exchange servers
might seem like a simple task (after all, Windows, Active Directory, and Exchange Server are