1. Jason Ding
  2. PowerBuilder
  3. Friday, 27 April 2018 18:35 PM UTC
I know that Powerbuilder can connect to SQL Azure via SQL Sever Native Client . I have a question: is it possible to build a local desktop Powerbuilder application but using SQL Azure(not an IWA deployed to Cloud)? If so, what is the limitation? Will it use the same database connection method an transaction object in application? Can I find a demo application?
Roland Smith Accepted Answer Pending Moderation
  1. Saturday, 28 April 2018 14:32 PM UTC
  2. PowerBuilder
  3. # 1
Comment
  1. Carlos Andres Rico
  2. Wednesday, 12 June 2019 23:56 PM UTC
Hi Mr. Smith... Could you please update the link ... It seems to be dead by now ... :(

  1. Helpful
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 13 June 2019 00:12 AM UTC
  2. PowerBuilder
  3. # 2

I deleted it because the dbparms changed and I no longer have an Azure account to test with.

I think it is something like this:

Driver={SQL Server Native Client 10.0};Server=tcp:[serverName].database.windows.net;Database=myDataBase;Uid=[LoginForDb]@[serverName];Pwd=myPassword;Encrypt=yes;

 

 

Comment
There are no comments made yet.
Carlos Andres Rico Accepted Answer Pending Moderation
  1. Thursday, 13 June 2019 16:13 PM UTC
  2. PowerBuilder
  3. # 3

Hi, Mr. Smith ...
Thanks a lot ! ... It was really helpful !!! ... 
I confirm our profile configuration as it worked !:

DBMS = "SNC SQL Native Client(OLE DB)"
ServerName = tcp:<ServerName>.database.windows.net
LogId = <UserID>@<ServerName>
LogPass = <Password>
...
DBParm = Database='<DatabaseName>',Provider='SQLNCLI10',Encrypt=1, ...

Comment
There are no comments made yet.
Michael Kramer Accepted Answer Pending Moderation
  1. Thursday, 13 June 2019 23:10 PM UTC
  2. PowerBuilder
  3. # 4

Hey Jason,

Technically, no problem. Albeit storing data offsite brings issues like latency, security, access control, and intermittent connectivity failures much more to the table than a local DB server within your physical building.

But even more, going global has legal implications that probably take longer to solve and may even sink your cloud strategy. Example:

  1. Danish company
  2. Cloud platform no. 1 offers DB hosted in Netherlands replicated to Ireland (or vice versa).
    Cloud platform no. 2 offers DB hosted in Denmark but replicated to US ground.
  3. Data stored includes personal identification and very sensitive data.
    Health records, high-risk sports activity, economic impact of workplace absence, and more.

Before going live, you need to find out how to handle all such data and whatever issues may arise.

TECHINCAL ISSUES =>  Don't hesitate to raise them in this forum.
LEGAL ISSUES => Seek legal advice, I'm not a lawyer.

HTH /Michael

Comment
  1. Roland Smith
  2. Friday, 14 June 2019 00:57 AM UTC
  1. Helpful
  1. Michael Kramer
  2. Friday, 14 June 2019 17:26 PM UTC
Nice link. THX /Michael
  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.