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

Resolved SQL native client support

  1. How-to
0
Votes
Undo
  1. Ganesan Rajan
    Ganesan Rajan
  2. PowerBuilder
  3. Thursday, 4 April 2019 09:16 AM UTC

Dear PB Community,

We migrated our application to PB 2017 (from PB12) recently and for DB connectivity(SQL Server 2016), we rely on SQL native client. As a prerequisite, customers have to install SQL Server 2008 R2 client in their machine to successfully launch our product.

Query1: With PB 2017, can we use Sql native client released with SQL Server 2012. According to microsoft, that was the last available version of Nativeclient. Does PB 2017 support the latest Native client?

Query2: Microsoft also suggests to use " Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL)" for further development to make use of new feature of SQL Server latest versions. Does PB2017 support this connectivity?

Thanks in Advance,

Ganesan R

India

 

 

References
  1. https://docs.microsoft.com/en-us/sql/connect/oledb/oledb-driver-for-sql-server?view=sql-server-2017
Silent Install for AutoCompile.exe
Powerbuilder 17 COM Port Communication Failure (Sa...
Accepted Answer
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Monday, 8 April 2019 10:19 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi Ganesan,

 

#1. PB 2017/2019 supports SQL Server 2012 Native Client, which is also available in the Provider drop-down list.

 

#2. Currently, we’ve discovered that there is some issue handling time(7) columns in a table when PB connects the DB using MSOLEDBSQL. We suggest that you work around this issue by adding DataTypeCompatibility=80 to SQLCA.DBParm.

As we haven’t done a comprehensive test against MSOLEDBSQL, please do a thorough test and see if everything works fine after you add DataTypeCompatibility=80 when using MSOLEDBSQL.

 

We currently recommend users to use SQL Server Native Client to connect to SQL Server 2016, which doesn’t have the issue with time(7) columns. But we still recommend you test your application and see if it has any other issue.

 

Regards,
Ken

 

Comment
Ganesan Rajan
  1. Ganesan Rajan
  2. Monday, 8 April 2019 12:57 PM UTC
Thank You for your information.
  1. Helpful
There are no comments made yet.
Responses (3)
Matthew Balent
Matthew Balent Accepted Answer Pending Moderation
  1. Monday, 8 April 2019 15:40 PM UTC
  2. PowerBuilder
  3. # 1

You might want to take a look at this Stackoverflow post.  Although it is using PB 12.5 it should still work with the more current versions.

Comment
Roland Smith
  1. Roland Smith
  2. Monday, 8 April 2019 16:54 PM UTC
Don't use TrustedConnection as it opens you up to Man in the Middle attacks. If you specify the full network name of the server with Encrypt = Yes, it will be able to establish a secure connection.
  1. Helpful
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 4 April 2019 12:47 PM UTC
  2. PowerBuilder
  3. # 2

The officially supported drivers are the ones that appear in the Provider drop-down on the SNC profile window. The new one is not in the drop-down.

You can use MSOLEDBSQL to make ODBC or OLE DB connections and assign it as the SNC provider in code.

It does work but it isn't officially supported. You'd have to test it in your app to see if there are any issues.

 

Comment
Ganesan Rajan
  1. Ganesan Rajan
  2. Monday, 8 April 2019 13:00 PM UTC
Thank You for your information.
  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.