
A Principled Technologies test report 14
Database performance and resiliency in the Intel processor-powered
Dell PowerEdge R630 running Microsoft SQL Server 2014
6. In the Specify Replicas page, under the Replicas tab, click the Add Replicas button and connect to the other
SQL Server instances that you joined as nodes in your Windows Server Failover Cluster. Configure the
following options:
Automatic Failover (Up to 2): Checked
Synchronous Commit (Up to 3): Checked
Readable Secondary: No
7. In the Endpoints tab, verify that the port number value is 5022.
8. In the Listener tab, select the Create an availability group listener option. Enter the following details.
Listener DNS name: Name that you will use in your application connection string
Port: 1433
9. Click the Add… button to provide an IP address. In the Add IP Address dialog box, enter your preferred
virtual IP address in the IPv4 Address field. Click OK. Click Next.
10. In the Select Initial Data Synchronization page, select the Full option. Provide a shared folder that is
accessible the replicas and that the SQL Server service account used by both replicas has Write permissions
to. This is just a temporary file share to store the database backups that will be used to initialize the
databases in an Availability group. If you are dealing with large databases, it is recommended that you
manually initialize the databases prior to configuring them, as your network bandwidth may not be able to
accommodate the size of the database backups. Click Next.
11. In the Validation page, verify that all validation checks return successful results. Click Next.
12. In the Summary page, verify all configuration settings and click Finish. This will create and configure the
AlwaysOn Availability Group and join the databases.
13. In the Results page, verify that all tasks have been completed successfully.
Configuring the database workload client
For our testing, we used a virtual client for the Microsoft SQL Server client. To create this client, we installed
Windows Server 2008 R2, assigned a static IP address, and installed .NET 3.5.
Configuring the database
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 40GB 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 2014. We built the 40GB database in SQL Server 2014, and then performed a full
backup, storing the backup file on the C: drive for quick access. We used that backup file to restore the server between
test runs.
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 performed the following steps:
Comentarios a estos manuales