There is a problem with Toad for SAP which causes issues during production releases which had DDL changes.
How to reproduce:
1, Open Toad -> and connect to a Sybase IQ server via Connection manager
- Go to View- > Object Explorer.
Now Check for table locks by using sp_iqlocks. You will see shared locks on ALL tables on the server, across all schemas.
Thus, if someone has a Toad session open during the release, any DDL on a tables such as alters, will fail with a table is in use error.
I don’t understand why Toad needs to lock all tables .
We have many Toad sessions connected, and this is not feasible for us to control everyone and tell them not to use Toad during the release.
Has anyone come across this issue and do you have solution ?
Version : Licensed Toad for SAP 3.1.0 bugs 1109