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

Resolved Connecting to AWS Database through PowerBuilder

  1. How-to
0
Votes
Undo
  1. Timothy Beck
    Timothy Beck
  2. PowerBuilder
  3. Thursday, 9 December 2021 14:57 PM UTC

Bruce,

I saw that you had a session recently about connecting PowerServer to AWS.  Unfortunately I missed it, but I was wondering how one might connect PowerBuilder to an AWS database (e.g. MariaDB).  I attempted to connect recently and was unable to do so.  My assumption is that it was lack of knowledge and I thought I'd reach out to an expert.  Any guidance would be appreciated.

Tim

  1. Amazon AWS
  2. PowerBuilder (Appeon)
PB not showing response from TRY CATCH from SQL Se...
Powerbuilder - Tab Control Color Settings
Responses (3)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 9 December 2021 21:03 PM UTC
  2. PowerBuilder
  3. # 1

Running client/server this way is probably going to perform bad, be unstable, and have security issues.  The recommended way is to use PowerServer 2021 if you want to deploy to the cloud, or at least use VDI in the cloud.

You can quickly experience what an app deployed by PowerServer is like running one of the demo apps.

As far as database, out of the commercial ones SQL Server is the most popular and out of open-source ones PostgreSQL.  Both of these are officially supported for client/server or PowerServer projects.

Comment
Load more comments
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 9 December 2021 22:28 PM UTC
Quite easy, and not that much different than client/server development. But of course, you can't just wing it. You'll need to spend the time to read through the docs.

First, make sure to understand the system requirements and comply with that: https://docs.appeon.com/ps2021/Installation_requirements.html

Then, I recommend first going through the Quick Start Guide and deploying one of the included demo apps: https://docs.appeon.com/ps2021/quick_start.html

Then, watch some of the Elevate 2021 replays: https://www.appeon.com/conference/elevate-2021/session-catalog.html

And finally, try it on your own app.
  1. Helpful 2
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Friday, 10 December 2021 00:48 AM UTC
Hi Armeen,

Great to find out that the replays are already available, thanks!

  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 10 December 2021 02:03 AM UTC
You're very welcome, and thanks for taking the time to attend the conference live!
  1. Helpful
There are no comments made yet.
Timothy Beck
Timothy Beck Accepted Answer Pending Moderation
  1. Thursday, 9 December 2021 19:59 PM UTC
  2. PowerBuilder
  3. # 2

Thanks Bruce!

It's actually not a cost issue, but a central DB issue.  My client has staff all over the country that need to access the application and I'm open to whatever database works best.  For SQL Server, would you use the native driver or continue to use ODBC. 

Tim 

Comment
Bruce Armstrong
  1. Bruce Armstrong
  2. Friday, 10 December 2021 03:51 AM UTC
Ah, I'm really talking about the database I would connect to from an app deployed to AWS. By default, the databases that you create in AWS are only accessible (as they should be) from an app also deployed to AWS.



Given that is the case. I would use the native driver. That's what I used in my sample.
  1. Helpful 1
There are no comments made yet.
Bruce Armstrong
Bruce Armstrong Accepted Answer Pending Moderation
  1. Thursday, 9 December 2021 18:49 PM UTC
  2. PowerBuilder
  3. # 3

I haven't worked with MariaDB.  In my session for Elevate I used SQL Server Express, both for my local project and in AWS.

My initial impression is that you would use an ODBC driver for it ( such as https://mariadb.com/kb/en/about-mariadb-connector-odbc/ ) just as you would for MySQL (which MariaDB is derived from).

For what it's worth though, my experience with using MySQL/MariaDB has always been painful, particular if you use a storage engine that doesn't support transactions.  I would opt for just about any of the other database options that AWS supports such as PostgreSQL, Oracle or SQL Server before going with MySQL or MariaDB.  The Amazon Aurora database is MySQL/PostgreSQL compatible and I'd probably even look at that as well.  That's just based on prior painful experience on my part, your mileage may vary.

Note that if you're looking at an AWS database to save licensing costs, only DynamoDB is free.  And because that one is NoSQL, you'd have to get a third party ODBC driver (usually at some cost) in order to talk to it from PowerBuilder.

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.