Natalia

Hi Sergei, thanks a lot for the quick response. We are actually using bulk insert now but trying to get away from file based uploads because the data that we generate is in memory and saving it to file is an unnecessary overhead. In the case of bulk insert the problem is complicated by the fact that the fs has to be mounted on both the client generating the file and the sql server, which is hard to achieve in cloud environments, bcp has its drawbacks too. Could you estimate how hard it would be to...

Hi, we are using OTL library for reading/writing to MSSQL Server from our C++ applications. We are looking for a way to optimize our bulk uploads (loading millions of rows in bulk). Our DBA recommended using native MSSQL bulk copy API . We would really like to use OTL rather than calling ODBC C functions directly, but I don't think OTL currently supports MSSQL bulk copy. Is it possible to add this support or is there anything we can use in OTL that will give comparable performance for bulk inserts....

Hi Sergei, Thank you so much for looking into that. I did some digging in Microsoft docs. According to it "SQLSetConnectAttr function now supports the use of the SQL_COPT_SS_TXN_ISOLATION attribute. Setting SQL_COPT_SS_TXN_ISOLATION to SQL_TXN_SS_SNAPSHOT indicates that the transaction will take place under the snapshot isolation level ". Those definitions seem to be driver specific. "The SQL Server Native Client ODBC driver supports a number of driver-specific extensions to ODBC connection attributes...

Hi Sergei, Thank you so much for looking into that. I did some digging in Microsoft docs. According to it "SQLSetConnectAttr function now supports the use of the SQL_COPT_SS_TXN_ISOLATION attribute. Setting SQL_COPT_SS_TXN_ISOLATION to SQL_TXN_SS_SNAPSHOT indicates that the transaction will take place under the snapshot isolation level ". Those definitions seem to be driver specific. "The SQL Server Native Client ODBC driver supports a number of driver-specific extensions to ODBC connection attributes...

Hi, we use OTL with SQL Server and it has isolation type called "snapshot" https://docs.microsoft.com/en-us/sql/t-sql/statements/set-transaction-isolation-level-transact-sql?view=sql-server-ver15 Looks like OTL doesn't support this level, is it easy to add? Thanks, Natalia

Good idea. Hopefully it will save hours of debugging to the next person who stumbles upon this issue :)

Thanks a lot, Sergei. Armed with your explanation, I checked SQLite ODBC documentation and found that there is a flag "BigInt" that can be set on the connection level. Adding this flag resolved the issue. I am adding the reference here in case anyone else has similar issues http://ch-werner.de/sqliteodbc/html/index.html Thanks again for the help!

Thank you for offering to provide the patch. I'd like to understand the scope first- will setting this conditional "ODBC int" macro affect the size of integers returned by other DB drivers as well or can it be limited specifically to the SQLite? I use SQL Server, Vertica and SQLite databases in the same code and I don't want to change the way my SQL Server and Vertica integers are processed. If this macro can be limited to SQLite integers specifically, that patch would really solve my problem.