Specifications

A Principled Technologies test report 21
Hardware upgrades to improve database, SharePoint, Exchange, and
file server performance with the Intel processor-powered Dell
PowerEdge T630
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 40GB 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
CREATE LOGIN [ds2user] WITH PASSWORD=N’’,
DEFAULT_DATABASE=[master],
DEFAULT_LANGUAGE=[us_english],
CHECK_EXPIRATION=OFF,
CHECK_POLICY=OFF
GO
h. We set the database recovery model back to full.
i. We created the necessary full text index using SQL Server Management Studio.
j. We created a database user and mapped this user to the SQL Server login.
k. We then performed a full backup of the database. This backup allowed us to restore the databases to a
pristine state relatively quickly between tests.
Running the DVD Store tests
We created a series of batch files, SQL scripts, and shell scripts to automate the complete test cycle. DVD Store
outputs an orders-per-minute metric, which is a running average calculated through the test. In this report, we report
the last OPM result reported by each client/target pair.
Each complete test cycle consisted of the general steps listed below. For each scenario, we ran three test cycles,
and reported the median outcome.
1. Clean up prior outputs from the server and all client driver systems.