Lock Timeout setting nav 4 sp2 / sp3

colin_leversuch-roberts

Wonder if members could clarify this setting for me please?
currently the lock timeout box is clear, but the value for timeout is set to 14400.
As I understand it with the checkbox clear this setting, 14400, is ignored - what isn't clear is what the default behavoiur is- is no lock timeout meaning the client waits forever or doesn't wait at all?

thanks.

bbrown

The default behavior is Lock Timeout = 0. Which means there is no Lock Timeout and the client will wait forever.

Waldo

Actually, when you install a new DB, you'll see that the default setting is:
- the checkbox = TRUE
- the timeout duration: 10s

At least in 5.0

DenSter

The purpose is to give you the choice: do you want the client to wait until locks are resolved (however long that takes) or do you want to give the user feedback after a while. It depends on user preference really, I've seen people who didn't like the message at all, they just wanted the process to complete. I've seen others who didn't want to wait forever.

kine

And of course do not forget about the TIMEOUT property you can set through code in some situations, e.g. running batches etc...

ajayjain

will it be ok to put anything between 200-500 in alter database for 300 concurrent users
any idea what are the plus and minus points for increasing and decreasing this.

Waldo

If you want people to wait for +200 seconds before they get the message to re-run the functionality because it is locked for the moment .. then yes, it's ok.

It's all about user experience:
do they want a message to be able to do something else? or do they want to wait (a little?) bit longer and not get the message.. .

We (I) can't answer that for you..