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.

60 Part I: Introduction to SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong><br />

Installing SharePoint Portal Server<br />

Installing SharePoint Portal Server 2003 is fairly intuitive. If you’re performing a simple<br />

installation, you can choose the default settings <strong>and</strong> have your environment up<br />

<strong>and</strong> running quickly. If you have to install SharePoint Portal Server on a domain<br />

controller—or if you’re installing in a larger, more complex environment—a few<br />

decision points will require a bit more explanation. A common example is deciding<br />

when to use a SQL Server database instead of the default MSDE database.<br />

When installing SharePoint Portal Server, many of the first installation steps are<br />

the same whether you plan to install with MSDE or with SQL Server. If you are<br />

implementing a fairly simple SharePoint Portal Server environment (one that won’t<br />

use over 2 GB of information in the portal site <strong>and</strong> has both SharePoint Portal Server<br />

<strong>and</strong> the database on the same machine), MSDE will probably be your best choice<br />

(unless, of course, you need to cluster your SQL databases, in which case SQL Server<br />

is required). One advantage of an MSDE scenario is that you don’t have to purchase<br />

SQL Server licenses. If, however, you need to install SharePoint Portal Server on a<br />

domain controller (DC), you must use SQL Server: MSDE is not supported on DCs.<br />

See Table 3-2 for guidelines on when to use MSDE or SQL Server.<br />

Table 3-2 Database Type Guidelines<br />

Condition Preferred Database Type<br />

If you require more than 2 GB of storage SQL Server<br />

If you are installing SharePoint Portal Server on a MSDE<br />

single server with fewer than 1000 sites<br />

If you require database to be located on a server other SQL Server<br />

than the server running SharePoint Portal Server<br />

If you do not have access to SQL Server, but want to MSDE<br />

work with SharePoint Portal Server<br />

If you plan to scale out into a server farm scenario<br />

or use any type of multiple-server implementation<br />

If you’re on a tight budget MSDE<br />

If you need a single-server deployment—for<br />

MSDE<br />

example, when you need to deploy a single<br />

server for application testing, for development, or<br />

as a proof-of-concept server<br />

SQL Server, because the MSDE<br />

database does not accept remote<br />

connections<br />

If you require the ability to cluster your databases SQL Server 2000 Enterprise Edition<br />

Please note that no database connector exists for databases other than MSDE or<br />

SQL Server (such as Oracle or Sybase) for SharePoint Portal Server–specific information.<br />

Therefore, such information—including document content, area configurations,<br />

user profiles, <strong>and</strong> other information generated or hosted by SharePoint Portal<br />

Server or Windows SharePoint Services—must be held in either a SQL Server 2000 or

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

Saved successfully!

Ooh no, something went wrong!