Hi, Is anyone else having problems connecting to a AWS Redshift Server? It just takes forever to load in the data model screen, which obviously makes the work quite painful. We have about 70 (seventy) tables in the data lake. Is that too many?

Hi John, there is no known issue at this time where clients are facing issues connecting to a AWS Redshift Server. Can you please confirm for us that the connection is successful after some time? 70 tables I believe should not be too many, however if your tables have many columns or complex schemas this might slow down visualisation in the data model editor.

Thanks @Michael Ullock - Any tips from you or the team on configuration on the RedShift side to speed up the connect and performance?

Please let me check this internally and get back to you ASAP

Hi John, I advise going over the recommendations for database performance improvement that can be found in our documentation here: https://www.gooddata.com/docs/cloud/connect-data/performance/

@Moises Morales Thanks for sending these. We are looking into them, but may need somethig a bit more specific. Will let you know.

We have now switched to postgresql, and we are now getting this message:

Raw error response
{
	"title": "Bad Request",
	"status": 400,
	"detail": "An error has occurred while calculating the result",
	"resultId": "7a8e7e0de5d413100d724cc2a7eff5ecdb99895b",
	"reason": "General error",
	"traceId": "1c7c422084e74522a18e2a5e449c13dd"
}

is it possible to get a more meaningful message that would help us find out the root cause of this issue?

Hi Oscar, I'm sorry for the delay on this. I've checked the error and can see the following: ERROR: permission denied for table ledger_load_plan