POSTGRES SSH TUNNEL DRIVER

One option creates ssh tunnel with using a terminal, then connect to the database with pgAdmin4 using the local port which you used when creating ssh tunneling. If your remote server ssh port is not 22 then you could not do this with pgAdmin. The problem is that we keep running into syntax problems with MS Query, I assume because we're using PostgreSQL instead of whatever MS Query uses, I literally can't even pull a single field out of certain tables without getting a syntax error. Follow these steps to connect PostgreSQL using SSH Tunneling at AWS: Open PuTTY. You can use SSH tunneling option with pgAdmin4 v3.1 if your remote server ssh port is 22. I know ODBC is supposed to be kinda slow, but it seems to work just fine with MS Query. I pulled one of our smaller tables that has 5 fields and 34 rows total, and it took more than 30 seconds in PowerBI.

However, when I try to use Power Query (or the equivalent in Power BI), it is unusably slow. I pulled one field out of our largest table, returning around 200,000 rows and it took less than a second. When I pull data through MS Query and dump it into Excel, it seems to work at a good speed.

POSTGRES SSH TUNNEL DRIVER

I'm pretty new to configuring and setting up data sources, with most of my industry experience being on the side of 'using existing data sources.'Īt the company where I work, our database is accessed through an SSH tunnel, and some Googling yesterday told me that downloading and installing an ODBC driver was probably going to be my best bet for being able to query the database within Excel and PowerBI.ĭriver installed just fine, and it does work.

Postgres ssh tunnel