Forum Discussion
Scheduled refresh for datasets linked to Azure Database for PostgreSQL requires gateway - why?
This post (which is now more than 2 years old) indicates that a gateway is required in order to do a refresh of datasets that are linked to Azure Database for PostgreSQL. From my testing today I assume this is still the case, as I always get 'Failed to update data source credentials: The credentials provided for the PostgreSQL source are invalid' when I try to change the data source credentials via the service. This seems like an unnecessary limitation given that using Azure SQL database doesn't require a gateway - are there any plans to fix this?
2 Replies
- Greg_Deckler
Community Champion
Actually, right now Azure SQL Database is requiring a gateway to refresh. Odd but that's what's going on right now. It's really just a matter of having the right drivers installed, Microsoft just can't install all of the drivers for every possible data source in the cloud gateway which they seem to be de-emphasizing lately quite honestly.
- AnonymousNot applicable
Firstly, I would like to say thanks smithae for the question. I think that it is super important.
The major thing that made me confused could be described like this.
In PBI Desktop, within Data Sources, Azure Database for PostgreSQL is listed. In that moment you think it is awesome I have nativ connector. After basic connection setup in PBI desktop you assume that everything is fine and ready to be published on service but then with the first refresh invalid credentials issue, that smithae mentioned "The credentials provided for the PostgreSQL source are invalid.", happened. Then after a long research I came up to your comment Greg_Deckler, that gateway is needed. In the same time the only logical explanation for me is the same thing that is written here.Why a gateway is needed - in even the same cloud environment - in parallel for Redshift is not needed?
Cheers,
Aleksa