Or is it TPS that locks?
When you save a query it triggers the TPS to refresh some of its metadata. Depending on which version you're using will depend on how much data is reloaded - this is something that has been reduced in recent versions. During this time the TPS will be unavailable and once loaded all other clients will download some of the new data. These two things will cause the other Consoles to freeze for a few seconds.
Hope that explains it!
It explains the behavior. The LANDesk Servicedesk used are using 7.3. The problem became apparent after the upgrade. It can cause delays so the other console client get time outs.
Yep I'm seeing this in 7.3 too.
Not sure I'd say this has improved since 726 but got worse.
This has always been a problem.
We were told to create a separate tps for admin/design/queries but that didn't help.
We upgraded to 7.3.2 and put a tps on a different server entirely. Still the same.
It means many of the great facilities in helpdesk are unusable.
I try and get in to work early and work the odd weekend but I have a huge backlog of queries/reports/dashboards/windows etc.
This is the main cause of issues I have with servicedesk and it really needs to be sorted.
I agree its a huge problem. All query design, window design, dashboard design work has to happen out of hours because of the significant impact on performance experienced by other users.
Its really not easy to maintain the system and implement small changes and tweaks in a large multi-user environment. Great if you can shout around the office, but really not workable with distributed users and timezones.
Has this been raised as a problem record yet?
Good question. Last time this was raised by us we were encouraged to raise an enhancement request which I don't think is the right move. I'm not even sure it's been formally acknowledged as an issue.
I agree with Julian, it appears to be worse in 7.3.x
I’m happy to report there are planned performance improvements in this and a number of other areas for the 7.4 release. I’ll be personally testing these at the first opportunity a beta build is available to ensure they satisfy concerns over being able to create or modify queries during working hours.