sm-shaw
commented
8 months ago I don't have access to Azure and am unable to reproduce this locally so far, so reproducing will need to be the first step.
I'm assuming in your example that:
diset('tpcc', 'mssqls_use_bcp', 'false')
was meant to be:
diset('tpcc', 'mssqls_use_bcp', 'true')
So as a start, this following script works for me locally (on Windows) using bcp and the Python interface.
print("SETTING CONFIGURATION")
dbset('db','mssqls')
dbset('bm','TPC-C')
diset('connection','mssqls_tcp','true')
diset('connection','mssqls_port','1433')
diset('connection','mssqls_azure','false')
diset('connection','mssqls_encrypt_connection','true')
diset('connection','mssqls_trust_server_cert','true')
diset('connection','mssqls_authentication','windows')
diset('connection','mssqls_server','{(local)\SQLDEVELOP}')
diset('connection','mssqls_uid','sa')
diset('connection','mssqls_pass','admin')
vu = 5
warehouse = 10
diset('tpcc','mssqls_count_ware',warehouse)
diset('tpcc','mssqls_num_vu',vu)
diset('tpcc','mssqls_dbase','tpcc')
diset('tpcc','mssqls_use_bcp','true')
print("SCHEMA BUILD STARTED")
buildschema()
print("SCHEMA BUILD COMPLETED")
exit()I run this as follows:
cd C:\Program Files\HammerDB-4.9
.\hammerdbcli.bat py auto ./scripts/python/mssqls/tprocc/mssqls_tprocc_buildschema2.pyNote that if some of the build works it is likely to be the item table that does not use bcp in any case as this is only 100K rows.
One difference is that my server name is wrapped with curly brackets {} so that special characters are not interpreted:
diset('connection','mssqls_server','{(local)\SQLDEVELOP}')
I have not tried connecting to SQL Server with the notation you are using:
someserver.database.windows.net
So it is possible that there is something here as the server name gets passed to the bcp procedure. Therefore one thing to try is to wrap any fields with potential special characters with curly brackets e.g.
diset('connection','mssqls_server','{someserver.database.windows.net}')
diset('connection','mssqls_uid','SOMELOGIN')
diset('connection','mssqls_pass','{SOMEPASSWORD}')If this doesn't work, I would try running the same using the Tcl script instead of Python to troubleshoot. We are using upvar to access variables from different levels, however this does work in my initial tests. If the Tcl script works and the Python one doesn't then this helps isolate the level the error is occurring at and in this case could be to do with upvarring to the incorrect level. (The variable should simply not be found in this case - bit it is worth eliminating)
If it fails in Tcl also the next step is to customise the script and modify the bcp procedure such as follows, this will then show you the variables it is being called with. This is particularly easy in the GUI, in the CLI you would use savescript to save the build script and then customscript to load it and run it interactively.
proc bcpComm { tableName filePath uid pwd server} {
upvar 3 authentication authentication
puts "authent:$authentication tabname:$tableName fpath:$filePath server:$server"
if {[ string toupper $authentication ] eq "WINDOWS" } {
exec bcp $tableName IN $filePath -b 500000 -a 16000 -T -S $server -c -t ","
} else {
exec bcp $tableName IN $filePath -b 500000 -a 16000 -U $uid -P $pwd -S $server -c -t ","
}
}Finally, to note that we have an open issue for a more elegant solution here: https://github.com/TPC-Council/HammerDB/issues/594 At the moment this is using the external bcp command that works, however we are passing the login parameters to the bcp utility a better solution as above would be to extend the odbc interface so we can login once and call bcp from ODBC. Unfortunately we are not there yet, but if we were doing this, this type of error would be unlikely.
arvindshmicrosoft
Guidance Bug reports are for when HammerDB is not behaving as expected. Bug reports should not be submitted for help in understanding database performance related questions. General questions on database performance or HammerDB usability should be submitted under Discussions.
Describe the bug Attempts to build a 100 warehouse TPCC database are repeatedly failing with error
A valid table name is required for in, out, or format options. The CLI does do some work, but serveral virtual users report this error and fail. FYI, the same CLI approach worked for generating 1000 warehouse and 5000 warehouse databases from the same client machine.This is an error from the
bcp.execommand. I'm not sure why the HammerDB code did not end up sending it the right parameters to bcp. If I don't use the bcp option within HammerDB, then the build does seem to complete, albeit much more slowly.To Reproduce Run the following script:
using
./hammerdbcli py auto ./scripts/python/mssqls/tprocc/mssqls_tprocc_buildschema.pyExpected behavior A 100 warehouse DB should have been successfully built.
Screenshots N/A - I am using the CLI.
HammerDB Version (please complete the following information):
HammerDB Interface (please complete the following information):
Operating System (please complete the following information):
Database Server (please complete the following information):
Database Client (please complete the following information):
Additional context