I am currently using SQL Workbench/J as my GUI to interface and run queries for BigQuery, however I'm running into a 10 second timeout issue when running more complicated queries. Any advice on how to increase the default timeout limit? Is it accessible/changeable from within the GUI? The error message I'm receiving is this:
[Simba]BigQueryJDBCDriver The job has timed out on the server. Try increasing the timeout value. [SQL State=HY000, DB Errorcode=100034]
(PS: I set up SQL Workbench/J using these steps and this driver)
When you define the ConnectionString you are able to add driver properties. Timeout is one of the properties you can use.
Simply add:
jdbc:bigquery://...;Timeout=3600;
Related
I discovered that since NHibernate 5.0 I can call the following code to delete all records of a table:
session.Query<T>().Delete();
It executes the code on the database without copying it across the network, which should improve performance a lot.
But this query times out.
I get the following error:
Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
I've tried setting the Connection Timeout setting in my connectionstring to 0 and to 3600, but it makes no difference.
My table only has about 200 records. But one column is a base64 encoded pdf, so it is quite big and the query would take a few seconds.
What else can I try?
It sounds like you need to increase the command timeout.
Note that there is a difference between connection timeout and command timeout.
You can set the default command timeout (in seconds) for ADO.NET commands created by NHibernate using the command_timeout NHibernate session configuration property. There are multiple ways to do that depending on what method you use to configure NHibernate. Here are the basics: http://nhibernate.info/doc/nhibernate-reference/session-configuration.html
I have a bit a funny situation. Our Azure SQL instance maxes out at 100 DTU for a certain query and the query returns a timeout:
SqlException (0x80131904): Timeout expired. The timeout period
elapsed prior to completion of the operation or the server is not
responding. This failure occurred while attempting to connect to the
routing destination.
If I run exactly the same query (with the parameters hardcoded) in SQL Server Management Studio it still takes the DTU up to 25%, but that's still far away from 100%. Nothing else runs on that server. There are a few other queries that run before/after. But if we just run them, nothing spikes out.
Any ideas?
My analysis of the issue goes like this..
First when DTU's are maxed out and if a query fails due to that,you will not get time out..Below is the error message you will get..
Resource ID: %d. The %s limit for the database is %d and has been reached. For more information
You can try testing that by opening multiple resource intensive queries
Secondly when you get time out's as indicated in your question,this is mostly due to query waiting for resources like say some database IO,memory..
we faced similar time out's ,but most of them are fixed by updating stats and rebuilding indexes,rest of them we optimized
I am using pentaho bi server 4.5 version, I have huge data for the particular tenant. When I am trying to generate report for particular period .. It is giving error as "Read Timeout" . And displaying as below :
ERROR
The requested URL could not be retrieved
While trying to retrieve the URL: http://xx.xxx.xx.xxx:8081/pentaho/ViewAction?
The following error was encountered:
Read Timeout
The system returned:
[No Error]
A Timeout occurred while waiting to read data from the network. The network or server may be down or congested. Please retry your request.
Please help me out.
And also need help on how to increase the read time on bi server.
Thanks in advance,
Mounesh
We can control the query timeout for PRPTs as follows.
Master Report > Attributes > query > timeout
Here you can define the how many seconds the report times out.
Master Report > Attributes > query > limit
Here you can define how many rows are returned to the report.
If using the Manage Data Sources Perspective in PUC you can add an extra property to set the query timeout.
This socketTimeout is valid for PostgreSQL and MySQL if you use any other DB let me know.
For further knowledge:
/biserver-ee/pentaho-solutions/system/mondrian/mondrian.properties
mondrian.rolap.queryTimeout=300
This accounts for Analyzer/ Mondrian timeouts.
We have got a large number of long running SQL queries and would like to be able to cancel the execution. So far, I am using an ExecutorCompletionService to run the queries, which works well for cancelling queries which are not yet run.
My problem is: I would like to hard-cancel the currently running queries too. The method java.sql.Statement.cancel() does not seem to work with HSQLDB. From the java doc: "Cancels this Statement object if both the DBMS and driver support aborting an SQL statement." I guess that HSQLDB does not support cancellation.
Does anyone have any idea how to cancel the statement anyways (in a possibly ugly, but still acceptable way)?
See https://sourceforge.net/p/hsqldb/bugs/1436/ for a working solution.
The short variant:
Use the newest SVN Version of HSQLDB or the 2.3.4 Final for the Server.
If the current query that you want to cancel is using a hsqldb connection, create a new connection with admin rights to the same server.
Use
select * from information_schema.system_sessions
to find the session with the statement you are looking for.
Use
ALTER SESSION <SESSIONNUMBER> RELEASE
to cancel the Statement.
Close the Connection.
For me the working sql command was ALTER SESSION <SESSIONNUMBER> END STATEMENT
I have a SQL job running which contains 2 steps. One of them is of type (T-SQL Script) and I am facing timeout issue with it.
How can I configure the timeout for that specific job? (eventually for the job if the timeout is inherited). I use SQL Server 2008 R2
Thank you!
As per my understanding there is no option to set time-ot for T-Sql script in SQL jobs.Mainy this will happen when ther is hughe increase in the records of the underlying sql script.
check this article.
http://www.simple-talk.com/blogs/2012/07/16/sql-server-query-time-out-when-referencing-data-on-a-linked-server-2/