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.

Chapter 11: Deploying a Single Server <strong>and</strong> a Small Server Farm 275<br />

Server 2000—that is, SQL Server must be installed prior to you starting the Windows<br />

SharePoint Services setup process. This installation scenario allows you<br />

to support a larger set of websites. When you use this method, you must perform<br />

additional steps to configure SQL Server <strong>and</strong> Windows SharePoint Services<br />

to work together. This is also true if you want to use SQL Server with<br />

SharePoint Portal Server. Refer to Chapters 2 <strong>and</strong> 3 for more information. Such<br />

additional steps could include the creation of additional accounts to use with<br />

SQL Server, configuring the SQL Server database to use Windows authentication,<br />

<strong>and</strong> connecting your extended virtual server to the SQL server where the<br />

configuration <strong>and</strong> content databases will be created.<br />

For either option, the database size required for Windows SharePoint Services<br />

depends on the number <strong>and</strong> size of the websites your server supports. You should<br />

not consider using WMSDE if you will need to store more than 2 to 4 GB of data, if<br />

you want the database placed on a different server than Windows SharePoint Services,<br />

or if you want to use Windows SharePoint Services search capability.<br />

(Although there is no upper limit to the size of databases when you use WMSDE,<br />

you might find that when databases get to a certain size it will be easier to manage<br />

them by using SQL Server.) For more information on capacity planning, please refer<br />

to Chapter 9, “Capacity Planning.”<br />

For more information on Windows SharePoint Services installation <strong>and</strong> configuration<br />

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

Caution During setup, in a default installation, Windows SharePoint Services<br />

extends the default virtual server (the default website in IIS) with Windows<br />

SharePoint Services. If you have a website running on the default<br />

website in IIS, Windows SharePoint Services will take over that website during<br />

installation. Also, before installing Windows SharePoint Services, verify<br />

that <strong>Microsoft</strong> FrontPage Server Extensions 2002 are not running on the virtual<br />

server on port 80. If FrontPage Server Extensions are running on the<br />

default virtual server, Windows SharePoint Services will not extend the virtual<br />

server during installation. (If you upgraded from <strong>Microsoft</strong> Windows<br />

2000 to Windows Server 2003, FrontPage Server Extensions were installed<br />

by default to port 80.)<br />

SharePoint Portal Server 2003<br />

For SharePoint Portal Server 2003, the single server runs the Web component, index<br />

component, search component, <strong>and</strong> the job server; <strong>and</strong> it optionally runs the components<br />

for backward compatibility with <strong>Microsoft</strong> SharePoint Portal Server 2001<br />

document libraries. SharePoint Portal Server 2003 is supported only on servers that

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

Saved successfully!

Ooh no, something went wrong!