SQL security in CA Datacom/DB can be used in addition to CA Dataquery security to control access to tables. If SQL security is activated at your site, users need to be assigned access to tables before they can access the data in the tables using CA Dataquery. For CA Dataquery SQL Mode, SQL security is the only access control in effect. If your site has an open security system, the security is open to all of your users unless access is specifically prohibited. If your site has a closed security system, the security is closed to all users unless specific access is authorized.
Note: In a closed security system, a user, known to SQL security as USERA, can execute an SQL statement CREATE TABLE USERB.TAB1 to create a table in the schema USERB. However, USERB would not be able to access this table until USERA grants the privileges through the GRANT command.
It is important that you communicate with your site Database Administrator to gain a clear understanding of the existing security systems and the current CA Datacom Datadictionary profile-codes. You should also make them aware of your needs for establishing a secure CA Dataquery environment. Ongoing communication is imperative, whereby you make your requests known (such as, requesting the creation of new profile-codes) and assure that any changes made within the CA Datacom security environment or in the CA Datacom Datadictionary profile-codes include appropriate plans for maintaining CA Dataquery data integrity and security.
If your site uses CA Ideal, meet with your Database Administrator to ensure that your signon procedures and standards for CA Dataquery security coordinate with those established for the CA Ideal system.
|
Copyright © 2014 CA.
All rights reserved.
|
|