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

Resolved PB 2017 and SQL Server 2017

  1. Issue
0
Votes
Undo
  1. Neil Sutter
    Neil Sutter
  2. PowerBuilder
  3. Monday, 5 March 2018 22:00 PM UTC

Does PowerBuilder 2017 support SQL Server 2017. 

I am running PowerBuilder 12.6 against a local (desktop) version of SQL Server 2017, release candidate 1 using the latest version of Native Client (any of them actually). So that might be a clue to the question.

But the client now wants to officially move to the actual released version of SQL Server 2017. Don't want to give an OK if there are any known issues between PowerBuilder 2017 and SQL Server 2017. 

May be an obvious question, but thought I'd better check just in case there are issues. 

Thanks. 

 

  1. Build
Postgres and carriage return
Account already logged in error
Responses (8)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 5 March 2018 22:20 PM UTC
  2. PowerBuilder
  3. # 1

Hi Neil;

    PB 2017 R2 states that only up to SS2016 is supported.  Appeon plans to QA & certify SS2017 in R3.

FWIW: I am using PB 2017 R2 with SS2017 via SNC with no issues on my PC's currently.

HTH

Regards ... Chris

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 27 September 2019 17:06 PM UTC
Update .. I am now using SNC from my PB2019 Apps with no issues against SS2017.
  1. Helpful
There are no comments made yet.
Govinda Lopez @Appeon
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Monday, 5 March 2018 22:40 PM UTC
  2. PowerBuilder
  3. # 2

Hi Neil,

 

With PowerBuilder 2017 R2 you can access the following Supported versions for SQL Server:

Microsoft SQL Server:

  • 2008 R2
  • 2012
  • 2014
  • 2016

databases using the SQL Native Client interface. The SQL Native Client interface uses a DLL named PBSNC170.DLL to access the database. The interface uses the SQL Native Client (sqlncli.h and sqlncli.dll) on the client side and connects using OLE DB.

To take advantage of these features, you need to use the SNC interface. The SQL Server 2016 or later SQL Native Client software must be installed on the client computer.

 

I hope this helps.

 

Regards,

Comment
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 7 March 2018 03:22 AM UTC
  2. PowerBuilder
  3. # 3

Adding to what Chris said, since SQL Server 2017 uses the same exact version of the native client as SQL Server 2016 so there should be no problems.  But technically speaking there is no warranty from Appeon on this combination.  Appeon plans to officially claim support for SQL Server 2017 in PB 2017 R3, which is scheduled for July 31, 2018.

Comment
There are no comments made yet.
David Peace
David Peace Accepted Answer Pending Moderation
  1. Friday, 27 September 2019 11:59 AM UTC
  2. PowerBuilder
  3. # 4

Hi Guys

I've just been doing some research on how we should be connecting to SQL Server 2016, I found this thread and it seems that people are saying that it's ok to use the native client with 2016.

However, as far as I can see there is not Native Client for 2016, version 2012 was the last Native Client? Am I missing something here?

Cheers

David

Comment
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 27 September 2019 14:13 PM UTC
  2. PowerBuilder
  3. # 5

About a year ago Microsoft un-deprecated OLE DB and released a new provider that also works in ODBC called MSOLEDBSQL. I've heard some people having issues using it with PowerBuilder, hopefully Appeon will fix those problems.

The SNC option in the DB Profile window doesn't show it in the drop-down but you can edit the profile in Regedit or use it in your application.

 

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

 

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 30 September 2019 18:49 PM UTC
I hear you but ... SNC has nothing to do with OLE is my point.

Its a direct call to the "sqlncli11" DLL DB client driver provided by MS.
  1. Helpful
Roland Smith
  1. Roland Smith
  2. Monday, 30 September 2019 19:10 PM UTC
If SNC has nothing to do with OLE DB, then why does it say "SQL Native Client(OLE DB)" at the top of the window?
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 30 September 2019 19:20 PM UTC
Confused Sybase "left-over" - LOL!
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 27 September 2019 18:58 PM UTC
  2. PowerBuilder
  3. # 6

Comment
Roland Smith
  1. Roland Smith
  2. Friday, 27 September 2019 20:44 PM UTC
My point is that MSOLEDBSQL should appear in the drop-down and be fully tested out and be a supported provider.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 30 September 2019 13:37 PM UTC
  2. PowerBuilder
  3. # 7

Hi Roland;

   FYI: Yes, the "MSOLEDBSQL" does appear. However, you need to choose the OLD-DB connection type (not SNC) l ...

HTH

Regards ... Chris

Comment
Roland Smith
  1. Roland Smith
  2. Monday, 30 September 2019 13:42 PM UTC
Yes, I knew that. My point is that it could also be used as a provider for SNC if it were to appear in the drop-down.
  1. Helpful
There are no comments made yet.
Dede Koueviakoe
Dede Koueviakoe Accepted Answer Pending Moderation
  1. Tuesday, 26 November 2019 14:15 PM UTC
  2. PowerBuilder
  3. # 8

Hi Chris,

can you copy and paste the configuration file with SQL Native Client, please (masking any password) ? 

Regards

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 26 November 2019 18:34 PM UTC
Hi Dede;

Here are the settings that I use with my SS2019 (I just replaced SS2017) in order to connect & work with that DBMS.



// Profile SS2019_Chris

SQLCA.DBMS = "SNC"

SQLCA.LogPass = <*****>

SQLCA.ServerName = "STD-CHRIS\SQLEXPRESS"

SQLCA.LogId = "Chris"

SQLCA.AutoCommit = False

SQLCA.DBParm = "Database='Chris',Provider='SQLNCLI11',AppName='PB2019',Host='STD-CHRIS',TrimSpaces=1,DelimitIdentifier=1,DateTimeFormat='yyyy-mm-dd hh:mm:ss:fff',TimeFormat='hh:mm:ss:fff',DateFormat='yyyy-mm-dd',TimeOut=5"



HTH ... Chris
  1. Helpful
Dede Koueviakoe
  1. Dede Koueviakoe
  2. Wednesday, 27 November 2019 08:56 AM UTC
Chris,

thanks a lot.

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