It is currently Thu Apr 24, 2014 8:57 am




Post new topic Reply to topic  [ 4 posts ] 
 FactorySQL Command Timeout 
Author Message
Corporal
Corporal

Joined: Tue Nov 03, 2009 8:32 pm
Posts: 37
Post FactorySQL Command Timeout
Hi

it seems that factorysql is using the default 30 second command timeout with sql server.

I have a group which executes every minute and take sometimes more than 30 seconds to execute, causing a timeout error. Could not find any option in the xml or the registry.

I am using FactorySQL 4.2.13 with sql server 2005. Any way to increase the Command Timeout?


Sun Aug 12, 2012 8:21 pm
Profile
Moderator
Moderator

Joined: Sun Apr 02, 2006 2:46 pm
Posts: 1982
Location: Sacramento, CA
Post Re: FactorySQL Command Timeout
I think the only setting for that would be on the database's JDBC driver as a extra connection parameter. Your query shouldn't take 30 seconds to complete. I would figure out why that is happening. Maybe your table is really large or doesn't have any indexes setup.

_________________
Travis Cox
Inductive Automation
Technical Support Rep.


Mon Aug 13, 2012 6:56 am
Profile WWW
Corporal
Corporal

Joined: Tue Nov 03, 2009 8:32 pm
Posts: 37
Post Re: FactorySQL Command Timeout
its a collection of queries inside a procedure which write a status value from the DB to multiple tags. So there are 50 variables being set by 50 queries to be written into tags.

Ofcourse I could split it up into two groups but ofcourse this scenerio can still occur sometimes if the table is busy. I know everything about indexes etc but there should still be a command timeout value somewhere to be set since factorysql seems to be using ADO Dotnet. There is only a connection timeout property in the connection string as far as i could check.

Any help?


Mon Aug 13, 2012 11:57 pm
Profile
Moderator
Moderator

Joined: Sun Apr 02, 2006 3:43 pm
Posts: 2418
Post Re: FactorySQL Command Timeout
Yes, what you're referring to is the IDbCommand.CommandTimeout property. However, there is no way to set this in FactorySQL. We found its implementation to be unreliable across various database connectors, at least back then.

Your best bet, if there really is no way to improve the table locking, may be to have FactorySQL (or your procedure) write to a buffer table, and then have some daemon move the data from there into the final table(s).

Regards,

_________________
Colby Clegg
Inductive Automation
Software Development


Tue Aug 14, 2012 9:33 am
Profile
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: