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

Resolved What is the recommended driver for MS SQL Server?

  1. Advice
0
Votes
Undo
  1. Daryl Foster
    Daryl Foster
  2. PowerBuilder
  3. Monday, 3 December 2018 05:35 AM UTC

Hi All,

Our application migration from ASE 16 to MS SQL Server is going well.  I've been using the SNC Native Driver, but I just want to make sure that is the recommended driver for connecting to MS SQL Server.  We are currently using MS SQL 2017 but will likely upgrade to MS SQL 2019.  We are currently using Appeon PB2017 R2.

I'm not 100% sure what the difference is between the native driver and the OLE DB driver which seem to be the two recommended ways of connecting from Powerbuilder.

Thanks.

How consuming .jar from power builder 2017 ?
Lost source code of OLE control
Responses (4)
Daryl Foster
Daryl Foster Accepted Answer Pending Moderation
  1. Tuesday, 4 December 2018 06:01 AM UTC
  2. PowerBuilder
  3. # 1

Thanks for the replies everyone.  I think I'm actually getting confused about what is a driver when talking about connecting to MS SQL.  Is it the DBMS or the Provider?  I had assumed the DBMS was the driver, but what is the difference if two different drivers can use the same provider?

 

For example, I can use either of these DBMSes

 

SQLCA.DBMS = "OLE DB"

or

SQLCA.DBMS = "SNC SQL Native Client(OLE DB)"

 

and they can both use the same provider:

 

SQLCA.DBParm = "PROVIDER='SQLNCLI11'...

 

Is one a better way to connect than the other?

Comment
There are no comments made yet.
David Peace (Powersoft)
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Monday, 3 December 2018 14:31 PM UTC
  2. PowerBuilder
  3. # 2

We have used SNC for sometime now and it works. ADO .Net was once the preferred method, but was a pain in deployment. Now it OLEDB, but to add to the confusion in PB the SNC connection is called:

SQLCA.DBMS = "SNC SQL Native Client(OLE DB)"

Does that mean that PB is actually using the OLEDB anyway, in which case there should be no difference?

Perhaps Appeon Tech can give us the definite answer to these two? What is actually being used underneath?

Cheers

David

 

 

Comment
Roland Smith
  1. Roland Smith
  2. Monday, 3 December 2018 14:48 PM UTC
It appears that the SNC is actually using the old OLE DB under the covers. If that is the case, they would need to add support for MSOLEDBSQL as the Provider. Currently they support SQLNCLI, SQLNCLI10, and SQLNCLI11.
  1. Helpful
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Monday, 3 December 2018 13:34 PM UTC
  2. PowerBuilder
  3. # 3

Microsoft has brought back the OLE DB driver as the preferred method under a new name. The old one is SQLOLEDB and the new one is MSOLEDBSQL. If you don't have it, you can download it from here:

https://www.microsoft.com/en-us/download/details.aspx?id=56730

 

Comment
There are no comments made yet.
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Monday, 3 December 2018 11:12 AM UTC
  2. PowerBuilder
  3. # 4

Hi Daryl,

contrary to my believe, it seems that OLE DB is the preferable way

https://docs.microsoft.com/en-us/sql/relational-databases/native-client/ole-db/sql-server-native-client-ole-db?view=sql-server-2017

https://docs.microsoft.com/en-us/sql/relational-databases/native-client/sql-server-native-client?view=sql-server-2017

Best,

.m

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 3 December 2018 15:43 PM UTC
Hi Marco;



FYI: Engineering just responded to me this weekend on this subject and said that they are going to be looking into adapting this newer OLE-DB driver in the PB2018 R2/R3 time frame. They are currently assessing the work estimates for this feature. This could also address the lack of a 64bit OLE-DB driver in the current PB release.



Regards ... Chris
  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.