Kbase 35334: Change In Progress SQL-92 Server Locking
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/15/2000 |
|
Solution ID: P5334
FACT(s) (Environment):
Windows NT 4.0
Progress 9.1D
SYMPTOM(s):
Cannot make schema changes when 4GL users have a share lock.
Cannot change security because the sqlexplorer cannot get an exclusive lock.
CHANGE:
Product Update Bulletin - H.1.3 Change In Progress SQL-92 Server Locking
In versions prior to Version 9.1D, the Progress SQL-92 Server locks at the
database connection level. This means that schema changes can only be performed
when no users are connected to the database.
With the release of Version 9.1D, the Progress SQL-92 Server locks at the transaction level. This new level of locking allows the DBA to modify database schema while there are active connections, as long as the users are not in active transactions.
FIX:
SQL, as per the sql standards, considers a transaction to be an action which is
accessing database data. Even though a transaction may just be reading data it is
still considered a transaction.
The classic 4GL viewpoint is that a transaction is an action changing database
data. This differs considerably from the standard sql concept.
If the 4GL application has a share lock, then it also has at a minimum, a share
lock on the database's schema.
A documentation bug has been entered to have the Progress Version 9 Product Update Bulletin modified, so that it clarifies what sort of transaction it's referring to.