SQL Command timeout

(0) Share

Report

Posted on by sanjaypandey20@live...

625

1) What should be fill in SQL Command Timeout field for NAV2013-R2, currently it is 00:30:00, can this is one of the cause of table locked problem.

2) What should be fill in Lock timeout duration, currently it is set 20 Sec.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (2)

Sort by

Suggested answer

Alexander Ermakov 28,096 on at

Like (0)

Report
Copy link

Link copied!

For normal work of production environment:

1) Depends how large is your database. For big databases the default 30 mins can be increases. If you just started you can live with the default settings.

2) If you are not experiencing any locking issues with the database, you can leave it like it is by default to 10 or 20. If issues - increase it to 30 or even 60.

For other operations, e.g. upgrades/synchronizations, you can increase the values as per your need (e.g., http://saurav-nav.blogspot.ru/2014/08/upgrade-nav-2013-r2-error.html)

Was this reply helpful? Yes No
Suggested answer

4BzSoftware 6,073 on at

Like (0)

Report
Copy link

Link copied!

Hi Sanjaypandey,

1) SQL Command Timeout: definition from Microsoft is the contextual time-out for a SQL command, msdn.microsoft.com/.../dd355055(v=nav.90).aspx. In my opinion, it is maximum time a SQL command can carry out. For some long tasks such as adjust cost, we need to increase this setting to hours, or days when upgrade NAV system.

2) Lock Timeout Duration: http://forum.mibuso.com/discussion/20281/lock-timeout-setting-nav-4-sp2-sp3 provides you more information.

Was this reply helpful? Yes No
Suggested answer

Suresh Kulla 50,280 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Sanjay,

I will leave both the setting values as you have now unless if you are running a big query which is taking very long time as other suggested during upgrade or may be adjust cost entries you don't need to change SQL Command TimeOut

By default the Lock Timeout Duration is 10 sec and increasing it 20 should be good but if you keep increasing this to higher value it may cause you delays and performance issues.

Are you encountering any issues currently ?

Was this reply helpful? Yes No
Verified answer

Tharanga Chandrasekara 23,118 on at

Like (0)

Report
Copy link

Link copied!

I would not recommend you to change the SQL Command Timeout. If you have a very valid reason for do that then you may proceed. On your second question you can increase it to a higher value, however then you will end-up with a performance issue. (Default 10s)

If you can let us know what you going to achieve by increasing the time then we might be able to help you out more.

Was this reply helpful? Yes No
sanjaypandey20@live... 625 on at

Like (0)

Report
Copy link

Link copied!

my problem is "ILE or G/L table locked by user", can this will help me to remove this problem.

Was this reply helpful? Yes No
Verified answer

Tharanga Chandrasekara 23,118 on at

Like (0)

Report
Copy link

Link copied!

I do not think it will help you to sort the issue. First need to check why system take considerable time to release the tables. You can do this by tracing SQL log or contact a SQL expert. They will be able to provide you the exact issue on the SQL side. There might be cases of deadlock which result the "lock by another user".

Other thing is check what is the costing method used in the system, if it is average and set as always then you might get the error as system try to adjust the cost for every transaction.

Was this reply helpful? Yes No