Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved SQL Server and PBMaxBlobSize in PB 2017 R2

  1. Issue
0
Votes
Undo
  1. Don Olliver
    Don Olliver
  2. PowerBuilder
  3. Wednesday, 13 June 2018 20:47 PM UTC

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

  1. SQL Server
  2. ODBC
Database connection
Pb 2019 to 2019R2
Accepted Answer
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 14 June 2018 13:35 PM UTC
  2. PowerBuilder
  3. # Permalink

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
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 22 February 2021 19:35 PM UTC
Hi Berka;

You would also need to deploy your PBODBnnn.INI file from your Development environment (where you made those Blob and/or Text changes) into the production deployment machine(s) where you also deployed your PB Run-time or place it in the same folder as the PB App's EXE. HTH

Regards ... Chris
  1. Helpful
Berka Frenfert
  1. Berka Frenfert
  2. Friday, 26 February 2021 11:34 AM UTC
Thanks you Chris. that help worked for me and saved my time.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 26 February 2021 20:48 PM UTC
That is "awesome" news Berka and you are most welcome! :-)
  1. Helpful
There are no comments made yet.
Responses (3)
Sailaja Jasti
Sailaja Jasti Accepted Answer Pending Moderation
  1. Thursday, 10 January 2019 01:03 AM UTC
  2. PowerBuilder
  3. # 1

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
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 10 January 2019 18:33 PM UTC
Hi Sailaja;

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

Regards ... Chris





  1. Helpful
There are no comments made yet.
Matthew Balent
Matthew Balent Accepted Answer Pending Moderation
  1. Thursday, 14 June 2018 11:51 AM UTC
  2. PowerBuilder
  3. # 2

Are you using the same driver as in 12.5?

Comment
Don Olliver
  1. Don Olliver
  2. Thursday, 14 June 2018 13:26 PM UTC
Yes, we are using 'ODBC Driver for SQL Server' to connect to a SQL Server 2014 database.

  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.