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

Resolved SQL Server Native Client Compatibility

  1. Issue
0
Votes
Undo
  1. Neil Sutter
    Neil Sutter
  2. PowerBuilder
  3. Thursday, 27 July 2017 14:02 PM UTC

Hi, 

Our PowerBuilder (12.6 at the moment) app has used SQL Server Native Client to connect to SQL Server 2005, 2008R2 and 2012. The client now want so to move to SQL Server 2014 and 2016. 

Microsoft appears to be confused and confusing in regards to its support of native client beyond SQL Server 2012. There are several Microsoft articles indicating that SQL Server versions beyond 2012 would not support the native client interface. However, articles such as this, written in July 2016: 

https://docs.microsoft.com/en-us/sql/relational-databases/native-client/applications/installing-sql-server-native-client

indicates that: "Microsoft SQL Server Native Client 11.0 is installed when you install SQL Server 2016". This would appear to indicate that SQL Server 2016 supports the native client interface. 

So, the obvious questions is, what is everyone else doing to connect a PowerBuilder application to SQL Server versions after 2012? 

TIA, 

Neil

 

  1. Client
  2. PowerBuilder
  3. SQL Server
PowerBuilder source code in SVN
FYI: Making International Payments
Responses (3)
David Peace (Powersoft)
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Wednesday, 2 August 2017 16:00 PM UTC
  2. PowerBuilder
  3. # 1

We have PB apps with SQL Server 2014 database and deploy the PB client with 2008r2 client. It might be worth looking at the ADO .Net connection as this comes with windows and so you do not need a client install at all.

We are looking at going down the ADO .Net route but have not yet committed the testing resorces to the project.

Hope that helps.

Comment
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 27 July 2017 15:30 PM UTC
  2. PowerBuilder
  3. # 2

Microsoft is not releasing newer version of the native driver than Microsoft SQL Server Native Client 11.0, but this version is able to connect and work fine with the latest SQL Server 2016.  In fact, in PB 2017 we certified both this driver and SQL Server 2016 as supported.  

So basically, this announcement from Microsoft basically means that if you stick with the native client you may not be able to take advantage of some new features they add to future versions of SQL Server that may require the DB client to accomodate, but overall your apps should keep working with newer versions.

In fact, when you intsall SQL Server 2016 there is option to install the 11.0 client.

Comment
Neil Sutter
  1. Neil Sutter
  2. Thursday, 27 July 2017 17:29 PM UTC
Thanks for the replies. Guess that makes sense based on what I can find from Microsoft - although they sure go out of their way to use double-speak about what works, what's supported, and what will be updated. In any regards, appreciate the responses. 

  1. Helpful
There are no comments made yet.
Michael Hartnett
Michael Hartnett Accepted Answer Pending Moderation
  1. Thursday, 27 July 2017 14:16 PM UTC
  2. PowerBuilder
  3. # 3

We have recently started using SQL Server 2014 in one client operation.  We have not had to install SQLNCI greater than 2008 R2 version, just the appropriate x86 or x64 version.

AFAIK, Powerbuilder (12.0, 12.5) does not support or use greater than that version.  Maybe someone can correct me or confirm.

Michael

Comment
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.