sm-shaw
commented
6 months ago -u doesn't seem to be an option in the version of bcp I checked, however this is on Windows and not Linux.
usage: bcp {dbtable | query} {in | out | queryout | format} datafile
[-m maxerrors] [-f formatfile] [-e errfile]
[-F firstrow] [-L lastrow] [-b batchsize]
[-n native type] [-c character type] [-w wide character type]
[-N keep non-text native] [-V file format version] [-q quoted identifier]
[-C code page specifier] [-t field terminator] [-r row terminator]
[-i inputfile] [-o outfile] [-a packetsize]
[-S server name] [-U username] [-P password]
[-T trusted connection] [-v version] [-R regional enable]
[-k keep null values] [-E keep identity values]
[-h "load hints"] [-x generate xml format file]
[-d database name] [-K application intent] [-l login timeout]with the error: certificate verify failed:self signed certificate it could be more likely to be the -T option to trust the server certificate, which we currently only have set for using Windows authentication.
proc bcpComm { tableName filePath uid pwd server} {
upvar 3 authentication authentication
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 ","
}
}Please advise if -T works instead or provide more details on the -u option if this is only available on the Linux version.
shane-borden
When building the schema against SQL Server 2022 the following error is encountered if
mssqls_use_bcpis set to true:To Reproduce Steps to reproduce the behavior: Execute the buildschema process using the following settings against a SQL Server 2022 instance:
Expected behavior buildschema should finish with no error
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 This error can be overcome by editing the proc "proc bcpComm" in
mssqlsoltp.tclto contain the-uoption: Current code:exec bcp $tableName IN $filePath -b 500000 -a 16000 -U $uid -P $pwd -S $server -c -t ","Updated code:exec bcp $tableName IN $filePath -b 500000 -a 16000 -U $uid -P $pwd -S $server -u -c -t ","There may be additional areas this needs to be updated. If the server does not require the option, having it specified anyway does not produce any errors.