Why must I use an odbc-connection type to connect to a postgres database in Power BI? - postgresql

Whenever I attempt to connect to my PostgreSQL database as a data source, I get the error message below.
Other users have recommended using an odbc connection? Why does an odbc connection work rather than a PostgreSQL connection for a PostgreSQL database in Power BI?
Had attempted to connect to my PostgreSQL database with all the correct credentials, failed with the error message mentioned. I had connected to the same database with an odbc connection perfectly.

Related

Has someone connected a PostgreSQL DB hosted in GCloud with Microsoft SSMS?

I have a question, I do not know how to solve it yet. Perhaps someone here has faced a similar issue.
We have a PostgreSQL DB hosted on Gcloud. We usually use a cloud proxy to connect with the database. It usually works very well!! In a nutshell the proxy connect a port from local host, to the actual DB host.
However this time, we want to connect it with Microsoft SSMS. We have not find an option where we can connect Microsoft SSMS with a DB running locally (this means connecting to a database on a port in local host).
The ultimate goal is to connect the database with Power BI. So if someone know how to connect a PostgreSQL DB hosted in GCloud to power BI that would also be very helpful!!
We have followed this tutorial:
https://www.anibalum.com.ar/2020/06/creating-linked-server-with-postgres.html
However we get the following error:
The linked server has been created but failed a connection test. Do you want to keep the linked server?
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "PAPERFLOWDB".
OLE DB provider "MSDASQL" for linked server "PAPERFLOWDB" returned message "[Microsoft][ODBC Driver Manager] Invalid connection string attribute".
OLE DB provider "MSDASQL" for linked server "PAPERFLOWDB" returned message "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified". (Microsoft SQL Server, Error: 7303)
We are using Microsoft SSMS v18.9.1

DB2 Connection is not working in DBeaver when i'm trying to connect

i'm trying to connect DB2 Database in DBeaver client, i tried with some of DB2 Drivers, but always it's showing the same error:
Error
My drivers:
Drivers
What could be the problem?

Postgres OLBC Connection error: FATAL: No pg_hba_conf entry

I am trying to create a linked server between the warehouse and a amazon cloud service.
The service provide is using a PostgreSQL database.
I have installed the ODBC Driver (12.10) on my server but I keep getting this error.
I am not sure how to work around this as I have never used Postgres before.

Connecting to Amazon RDS PostgreSQL Database from a VB.net Application

Can you help me to connect to Amazon RDS PostgreSQL Database from a VB.net Application. I already using a Npgsql .net data provider to connect to a local database.I am using the following connection string but getting a error message like
"Failed to establish a connection to
'ec2-dynanet-tomcat-new.cas1xn8fsgaw.ap-southeast-2.rds.amazonaws.com'."
conn = New NpgsqlConnection("Host=ec2-dynanet-tomcat-new.cas1xn8fsgaw.ap-southeast-2.rds.amazonaws.com;port=22;Username=xxx;Password=xxxx;Database=esurvey2")
Security Rule Screenshot

Connecting Tableau to Heroku Follower Database

Have created a follower database for a Heroku Postgres DB. I am able to connect to the follower DB by using pgAdmin, no problem.
When I try to connect with Tableau 8.2 Postgres connector using the same credentials, I get "no pg_hba.conf entry for host xxx.xxx.xxx.xxx, user yyyyyyyy, database zzzzzzzz, SSL Off".
As an alternative I tried the Amazon Redshift connector with the same credentials and it works, except for full drill through to underlying data errors out ("Syntax error at or near 7500") or some other line number.
Does anyone know a way to connect to Heroku Follower database with Tableau 8.2 that enables drill through (view underlying data)?
Have you been able to get the Postgres connector to work?
Is there a way to get the Amazon Redshift (or other) connector to work with drill through capabilities?