Kbase P22446: How to prevent a SQL-92 connection to write or update a record in the database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/05/2009 |
|
Status: Verified
GOAL:
How to prevent a SQL-92 connection to write or update a record in the database
GOAL:
How to prevent a ODBC connection to write or update a record in the database
GOAL:
How to prevent a JDBC connection to write or update a record in the database
GOAL:
How to make a Read Only client connection using SQL-92
GOAL:
Can -RO parameter be used with SQL-92 clients
GOAL:
Do the SQL-92 Server processes support the use of the -RO Read Only parameter?
GOAL:
How to set an ODBC connection to read only
GOAL:
How to set the Default Isolation Level of an ODBC Data Source to READ UNCOMMITTED
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
FIX:
The -RO (read only) Client parameter cannot be used with a SQL-92 ODBC connection. There are two methods for allowing read-only access to the database via SQL-92:
1) If you want a client to have read-only access, the Default Isolation level for the client must be set to READ UNCOMMITTED. To change the Default Isolation level on Windows, choose the appropriate DSN entry on the ODBC Administration and press the configure button. In the setup properties, go to the Advanced tab. Press the down arrow of Default Isolation Level properties box and select 'READ UNCOMMITTED'.
2) The DBA can GRANT SELECT privileges to users to give them read-only rights. By default non-DBA users do not have any privileges.