1. Don Olliver
  2. PowerBuilder
  3. Wednesday, 13 June 2018

We are connecting to SQL Server using ODBC Driver 11. Any embedded SQL using SELECTBLOB or UPDATEBLOB truncates data at 32K, which is the default for a SQL Server driver.

I have been unable to modify the default size to 1 GB, either by setting PBMaxBlobSize in pbodb170.ini or in the transaction object's DbParm property.

In the INI file, we set 

PBMaxBlobSize='1073741824'

in sections [Microsoft SQL Server] and [SQL Server]. 

For DbParm, I have tried

ConnectString='DSN=esepicdev11_mssql_2014;PBMaxBlobSize=1073741824'

and 

ConnectString='DSN=esepicdev11_mssql_2014',PBMaxBlobSize=1073741824

 

In PB 12.5, we only had to set the parameter in pbodb125.ini to get this to work. What am I missing?

Thanks,

Don Olliver

Who is viewing this page
Accepted Answer
Chris Pollach Accepted Answer Pending Moderation
1
Votes
Undo

Hi Don;

   The PBMaxBlobSize parameter in the SQLCA.DBParm field is only supported when using the ADO.Net, OLE DB or SNC SS db drivers. For ODBC db driver, you need to change the values in the PBODB170.INI file, adding the PBMaxBlobSize and also possibly PBMaxTextSize entires with their appropriate values.

  Please also note that the instance of the PBODB170.INI file you need to change in the development environment should be located in the "C:\Users\\AppData\Local\Appeon\PowerBuilder 17.0" folder. The PBODB170.INI file located in the "C:\Program Files (x86)\Appeon\Shared\PowerBuilder" installation  folder is not used by the IDE. This change of working INI file location was introduced back in the PB 12.6 days.

HTH

Regards ... Chris

 

Comment
Hi Chris,



Moving PBODB170.INI to C:\Users... solved this issue. Thank you!



Don

  1. Don Olliver
  2. Thursday, 14 June 2018
    

  1. Chris Pollach
  2. Thursday, 14 June 2018
There are no comments made yet.
  1. Thursday, 14 June 2018
  2. PowerBuilder
  3. # Permalink
Sailaja Jasti Accepted Answer Pending Moderation
0
Votes
Undo

We are having problems with SYC driver.

Though the @@textsize is set to 131072 and SQLCA.DBParm = "DBTextLimit='65536'" in database profile, the text column is still truncating to 32768 when datawindow is created.

If size is reduced by changing  SQLCA.DBParm = "DBTextLimit='5000'"  then the datawindow shows the column correctly with 5000 char when it is created.

What I am missing?

Comment
Hi Sailaja;

DWO's cannot process more than 32K. You need to use Select/Update BLOB commands instead.

Regards ... Chris





  1. Chris Pollach
  2. Thursday, 10 January 2019
There are no comments made yet.
  1. Thursday, 10 January 2019
  2. PowerBuilder
  3. # 1
Matthew Balent Accepted Answer Pending Moderation
0
Votes
Undo

Are you using the same driver as in 12.5?

Comment
Yes, we are using 'ODBC Driver for SQL Server' to connect to a SQL Server 2014 database.

  1. Don Olliver
  2. Thursday, 14 June 2018
There are no comments made yet.
  1. Thursday, 14 June 2018
  2. PowerBuilder
  3. # 2
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.