How to solve QuickSight SQL exception timeout error - amazon-athena

I have created a VIEW in Amazon Athena using:
CREATE OR REPLACE VIEW sentiment_analysis AS
SELECT
file,
Sentiment,
SentimentScore.Positive AS Positive,
SentimentScore.Negative AS Negative,
SentimentScore.Neutral AS Neutral,
SentimentScore.Mixed AS Mixed
FROM "targeted_sentiment_output"."sentiment_results"
The VIEW works and populates with the data.
I am now trying to load this into Amazon QuickSight, but get the following error:
Your database generated a SQL exception. This can be caused by query timeouts, resource constraints, unexpected DDL alterations before or during a query, and other database errors. Check your database settings and your query, and try again.
I think it may be a timeout error. I have tried to find the Advanced Settings tab to increase the query timeout limit but can't find it. Please can you provide clear instructions on where to locate the timeout limit?
If it is a different error then please explain...
Thanks!

Related

Dialog Flow Logging to Big query table invalid schema

I am using google cloud logging to sink Dialog flow requests data to big query. It works for the first 3-4 request but then gives the following Error.
Error Detail
Field jsonPayload.queryresult.responsemessages.payload.richcontent is a list of lists, which is not supported by Bigquery.
How can I solve this problem ?

Loading a Power BI query but getting a bunch of errors caused by other queries

I have a Power BI dashboard that has over 30 different queries. I just needed to load a new Kusto query and do not wish to do anything with the other queries that were existing.
But when I load the one query I am interested in, all of the other queries appear also in the "Load" pop up. After a while, I get a bunch of "failed to save modifications....Error returned: 'OLE DB or ODBC error' " messages from the other queries
I even went through all of those queries and selected "do not refresh" just so Power BI will just focus on the one query I need to load
The other queries really don't appear to have issues, since they refresh okay when refreshed individually. I have attached the error message. The one with the name "Query" is the only one that I wish to load
Does anyone have any idea how I can simply load the one query that I am interested in loading? I have attached the error message example below

Datastudio can not connect to your dataset, permissions or bug?

I got the read access on a dataset in bug query. However when I try to connect it in data studio. I get a configuration error.
Tried reconnecting the dataset and even though i can access the dataset if i login in BigQuery.
Any ideas, if I need any special permissions to connect that dataset to from datastudio?
If you get configuration error on any shared dataset make sure you have Viewer Permission. BigQuery Viewer Permission will not work for this.

How to fix 'Request contains an invalid argument' error when scheduling queries in BigQuery UI

I'm setting up a scheduled query in the new BigQuery UI as the project owner and have enabled the data transfer API. The query itself is a very simple SELECT * FROM table query written in standard SQL. The datasets I'm using are in the same region.
No matter how I set up the schedule options (start now, schedule start time, daily, weekly, etc.) or the destination dataset/table, I always get the same error:
"Error updating scheduled query: Request contains an invalid argument."
I have no idea which argument is invalid, it gives no more detail than that.
How do I solve this problem?
By trying to schedule the query in the classic BigQuery UI, it shows a more descriptive error which illustrates the issue:
Error in creating a new transfer: BigQuery Data Transfer Service does not yet support location northamerica-northeast1.
The data must be stored in either the US or the EU at this time, it seems.

The request has exceeded the allowable time limit Tag: CFQUERY

The query returns only 4-5 rows. It takes less than 1 second to execute. I have trid increasing the timeout of both cfquery and cfsetting but not working. most of the time code runs successfully but i got this error after every 20-30 request. I am using sql server database. I know when you restart the cf server or db server timeout issue occurs sometimes but this error is comming without restarting of any service (cf or sql server). I think there should be some setting changes in cf server please suggest.
The request has exceeded the allowable time limit Tag: CFQUERY
The error occurred on line 180.
<CFQUERY NAME="Sections" DATASOURCE="abcd">
SELECT * FROM News_Sections where Section = 'Home' ORDER BY Page_order
</CFQUERY>
The likely problem here is going to be the database not ColdFusion. I have a couple of tips for you. First, using the MSSQL Activity Monitor check out blocks (as a wait type). If you see a block or a "head blocker" click on that item and it will show you the query (sometimes :).
Once you locate it, fixing the problem will involve indexing or changing the query (complex joins or sub-queries often have unexpected consequences).
You might have some luck using "WITH(nolock)" in the above query to allow for a dirty read (probably ok if you are just getting categories). You might also consider caching the above query using cachedwithin or placing it in the application scope. If it is just broad "home" categories that seems reasonable to me (though obviously I don't know your schema.
My final bit of advice is to examine the page on which the error takes place closely. Sometimes the line number is off a bit. If you have groups of queries together it may not be the query you think is erroring out but the one above it. It's not common but it can happen.
As was pointed out by Mr. Bracuk, this may not be a problem with your query. This error has to do with the setting in the CFAdmin for Request timeouts. It is the page that is loading that has experienced the timeout and thrown the error. When the timeout occurred it just happened to be processing your query.
So, while the query is a good place to start looking, make sure to examine the entire script when searching for the cause of the timeout.