MS SQLServer OLEDB error trapping

[Samad Sodul]

Hi
I can add that the latest OLEDB driver is faster than latest ODBC driver connecting TD63/SQLSERVER 2017.

I run a Payroll Calculation for 250 employees
a) ODBC : 1mn 30 secs
b) OLEDB : 47 secs

I re-worked my libraries which help me to swap from ODBC/OLEDB or OLEDB/ODBC easily.

Thanks Steve for providing me the hint from example OLEDBSample_INSERTandSCROLL_TD63 some months ago.

Cheers
Samad Sodul
Ebene
Mauritius

[Steve Leighton]

.
Thanks Samad for the OLEDB speed confirmation for SqlServer.
I agree that the latest driver is a lot faster than ODBC. esp. when the SSPROP_INIT_PACKETSIZE is tweaked accordingly.
And for no need for a messy Sql.ini on every client.

[Samad Sodul]

Dear Steve,
I am not an expert in TD. Only to confirm if I am doing it right for OELDB.

Can you share a sample TD program for OLEDB connecting to SQL Server to catch the SQL Error, ( That is a piece of code for Begin Transaction, DBP_AUTOCOMMIT, Rollback, When SQL Error).

Thanks a lot

Samad

[Steve Leighton]

Samad said:
Can you share a sample TD program for OLEDB connecting to SQL Server to catch the SQL Error,

Simple OLEDB error trapping example attached

TD_OLEDB_ErrorTrapping.zip

[Samad Sodul]

Thanks a lot Steve for this example.

Best Regards

Samad

[a_sivababu]

I feel there is no need for sql.ini for any router if the router dll is directly passed to SqlDatabase as it is below.

Set SqlDatabase="ConnectionString:comdll=sqlodb32;dbname=MSSQLDB"

All other required parameters can be set through SqlSetxxxxxx().

I am not sure SetZeroLengthStringToNull is supported to be appended in ConnectionString in SqlDatabase. I have raised ticket on this sometime back but not sure whether this is resolved now.

Thanks
Siva A

[Steve Leighton]

.

Siva says:
there is no need for sql.ini for any router

Siva Thanks for the tip.
Assume you're referring only to ODBC routers, as unfortunately only works with ODBC - not TCP/IP ( comdll=sqlws32 ) as in the case of SQLBase native router.

But good to know if using odbc.
Thanks

[a_sivababu]

Hi Steve,
I haven not tried for SQLBase but It should work for Sqlora32, Sqlodb32, sqlsyb32,sqlifx32.

In case of SB Native router, I am not sure how clientruntimedir works if you have more than on SB since this parameter can not be set through coding.

Thanks
Siva A

[Igor Ivanovic]

Hi all,

FYI, this works for SQLBase also!
I use it like this:

Code: Select all

 Set SqlDatabase = 'ConnectionString: data source=' || gbl_sWindowsServerName || ';transport=tcpv4;port=2155;servername='|| gbl_sSQLBaseServerName || ';dbname=' || gbl_sDatabaseName'

I couldn't find it in the docs, but was made aware of it by OT support.
For some reason it still does require you to have a generic sql.ini, didn't had time to investigate this, maybe it's because my country settings, or I have a hidden connect buried in my classes before the string was set up in my monstruous app.