Re: Modifying system tables

In <40vt3p$l0m@aztec.co.za> storm@aztec.co.za (Storm Software) writes: >Just be very careful and make sure that your where clause >in your Permission program has 'and tabid > 100' in it. >Travis Rayhons (trvsryhn@dordt.edu) wrote: >: I am developing a database of all the permissions of my users to >: each database that they use. This way I can determine what >: permissions that each user has and keep access to certain databases >: very secure by revoking everyone else. >: I was wondering what harm or side effects could be had if I >: directly modify the tables: sysusers, systabauth, syscolauth. >-- In my workgroup, we run a daily security update system across our 6 Online servers, and the many databases therein. The program directly revokes/grants all permissions on all databases, controlled by a security database that only informix has access to. It took a bit of doing to smooth out the rough spots in the process. Be VERY careful about directly modifying system tables...if you have Informix support and mess up your database mucking about in there, chances are they won't help you fix it. It is possible as DBA of a database to revoke everyones permissions, including your own...if you don't fix the permissions before you exit, it may be impossible to fix without restoring the entire database. -- ds5419@panix.com Funk As Puck Productions Jesus Died For My Sins and All I Got Was This Lousy .sig