Home > Integrated Products > Microsoft HCI Solutions from Dell Technologies > White Papers > Building a Hybrid Database-as-a-Service Platform with Azure Stack HCI > Appendix B: HammerDB CLI configuration
This section describes how we configured the auto build and auto drive dictionary parameters for the testing.
dbset db mssqls
diset connection mssqls_server 10.129.80.xxx
diset connection mssqls_tcp true
diset connection mssqls_port 1433
diset connection mssqls_authentication sql
diset connection mssqls_odbc_driver ODBC Driver 18 for SQL Server
diset tpcc mssqls_count_ware 200
diset tpcc mssqls_num_vu 30
vuset logtotemp 1
TPC-C baseline configuration – for every environment – for every test
Table Name | Row Count |
[dbo].[customer] | 6000000 |
[dbo].[district] | 2000 |
[dbo].[history] | 6000000 |
[dbo].[item] | 100000 |
[dbo].[new_order] | 1800000 |
[dbo].[order_line] | 59993622 |
[dbo].[orders] | 6000000 |
[dbo].[stock] | 20000000 |
[dbo].[warehouse] | 200 |
As part of our test harness automation, we also dynamically built the HammerDB CLI .tcl code before each test run. Following is the template.
diset connection mssqls_linux_server <sqlip>
diset connection mssqls_tcp true
diset connection mssqls_port <sqlport>
diset connection mssqls_linux_authent sql
diset connection mssqls_uid <sqluser>
diset connection mssqls_pass <sqlpass>
diset connection mssqls_linux_odbc {ODBC Driver 18 for SQL Server}
diset connection mssqls_encrypt_connection true
diset connection mssqls_trust_server_cert true
diset tpcc mssqls_dbase <sqldb>
diset tpcc mssqls_driver timed
diset tpcc mssqls_total_iterations 10000000
diset tpcc mssqls_rampup <rampuptime>
diset tpcc mssqls_duration <testduration>
diset tpcc mssqls_checkpoint false
diset tpcc mssqls_timeprofile true
diset tpcc mssqls_allwarehouse true
vuset logtotemp 1
tcset logtotemp 1
tcset timestamps 1
As businesses grow, the amount of data and data transactions grows as well. Therefore, data infrastructure must predictably handle this growth. To assess this, a test was run using the HammerDB TPROC-C workload, scaling from 5 to 25 users, in increments of 5.
Our total duration run time, per virtual user group, is 6 minutes. Autopilot was configured as follows:
puts "TEST STARTED"
foreach z { <userload> } {
puts "$z VU TEST"
vuset vu $z
vucreate
puts "TCOUNTER STARTED"
tcstart
tcstatus
vurun
runtimer <singleruntimeinsec>
vudestroy
after 5000
}