16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

276 Part IV: Deployment Scenarios<br />

are members of a <strong>Microsoft</strong> Windows NT 4.0, Windows 2000, or Windows Server<br />

2003 domain. When you install SharePoint Portal Server 2003, setup automatically<br />

installs Windows SharePoint Services if it is not already installed. The single-server<br />

database options would be as follows:<br />

■ WMSDE. In SharePoint Portal Server 2003 setup, choose to install SharePoint<br />

Portal Server with the database engine on the server. This installs the MSDE to<br />

store the databases. WMSDE has the same limited throughput ability <strong>and</strong><br />

capacity with SharePoint Portal Server as it has with Windows SharePoint Services,<br />

as discussed in the previous section. It supports databases with a maximum<br />

size of 4 gigabytes (GB). If your deployment requires significant<br />

scalability or must store more than 2 to 4 GB of documents, you should use<br />

SQL Server in your deployment.<br />

■ SQL Server. This server has SQL Server installed prior to the start of the<br />

SharePoint Portal Server installation process, <strong>and</strong> then in the installation process<br />

you choose the option to install SharePoint Portal Server without the database<br />

engine on the server.<br />

For more information on SharePoint Portal Server 2003 installation <strong>and</strong> configuration<br />

considerations, please refer to Chapter 3.<br />

Database Automation <strong>and</strong> Maintenance<br />

Once you have installed Windows SharePoint Services or SharePoint Portal Server<br />

on a single server, the deployment is not complete until you have set up maintenance<br />

tasks <strong>and</strong> operational procedures. This is another differentiating aspect that<br />

you should take into consideration when you choose between WMSDE <strong>and</strong> SQL<br />

Server.<br />

You can complete many of the tasks needed to maintain <strong>and</strong> back up Windows<br />

SharePoint Services <strong>and</strong> SharePoint Portal Server 2003 by using the administration<br />

Web pages. (See Chapter 10, “Performance Monitoring in <strong>Microsoft</strong> Office Share-<br />

Point Portal Server 2003,” Chapter 28, “Disaster Recovery in SharePoint <strong>Products</strong> <strong>and</strong><br />

<strong>Technologies</strong>,” <strong>and</strong> Chapter 29, “Usage Analysis Tools in SharePoint <strong>Products</strong> <strong>and</strong><br />

<strong>Technologies</strong>.”) However, there are other SQL Server administrative tasks that you<br />

might want to complete, especially if the website is heavily used, business critical, or<br />

has a high profile. Using the SharePoint Portal Server Central Administration pages,<br />

such database-specific tasks that are not available include backing up the system<br />

databases, monitoring processes, checking for database errors, <strong>and</strong> the ability to<br />

alert someone when database-related events occur.<br />

The automation <strong>and</strong> maintenance of database administration tasks is easier<br />

with SQL Server than with WMSDE. You can manage SQL Server 2000 installations<br />

by using the SQL Server Enterprise Manager, which allows for local <strong>and</strong> remote management<br />

of SQL Servers. It also includes administration wizards that are designed to

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!