Specifications

A Principled Technologies test report 22
The datacenter in a box performance test: Comparing Dell and HP
blade solutions
13. Choose Create a new server farm, and click Next.
14. Enter the name of your existing database instance on the same application server.
15. Specify a username and password, and click Next.
16. Enter a passphrase into the Passphrase and Confirm Passphrase fields, and click Next.
17. Leave the default settings on the Configure SharePoint Central Administration Web Application screen, and click
Next.
18. Verify your settings, and click Next.
19. When the wizard has completed the configuration, click Finish.
20. Choose Run the farm configuration wizard on the Central Administration site.
21. Choose the services you wish to include in your server farm, and click Next.
22. Enter the specifications for the new site, and click OK.
23. Click Finish.
Configuring the database (DVD Store)
Data generation overview
We generated the data using the Install.pl script included with DVD Store version 2.1 (DS2), providing the
parameters for our 100GB database size and the database platform on which we ran: Microsoft SQL Server. We ran the
Install.pl script on a utility system running Linux. The database schema was also generated by the Install.pl script.
After processing the data generation, we transferred the data files and schema creation files to a Windows-
based system running SQL Server 2008 R2 SP1. We built the 100GB database in SQL Server 2008 R2, and then performed
a full backup, storing the backup file on the C: drive for quick access. We used that backup file to restore to the servers
between test runs. We performed this procedure once.
The only modification we made to the schema creation scripts were the specified file sizes for our database. We
explicitly set the file sizes higher than necessary to ensure that no file-growth activity would affect the outputs of the
test. Besides this file size modification, the database schema was created and loaded according to the DVD Store
documentation. Specifically, we followed the steps below:
1. We generated the data and created the database and file structure using database creation scripts in the DS2
download. We made size modifications specific to our 100GB database and the appropriate changes to drive
letters.
a. We transferred the files from our Linux data generation system to a Windows system running SQL
Server.
b. We created database tables, stored procedures, and objects using the provided DVD Store scripts.
c. We set the database recovery model to bulk-logged to prevent excess logging.
d. We loaded the data we generated into the database. For data loading, we used the import wizard in SQL
Server Management Studio. Where necessary, we retained options from the original scripts, such as
Enable Identity Insert.
e. We created indices, full-text catalogs, primary keys, and foreign keys using the database-creation scripts.
f. We updated statistics on each table according to database-creation scripts, which sample 18 percent of
the table data.
g. On the SQL Server instance, we created a ds2user SQL Server login using the following Transact SQL
(TSQL) script:
USE [master]
GO