We are getting ready to start replication testing on our development server under SQL Anywhere 12. This is a database that we migrated in stages from ASA6 up to SQL Anywhere 12.
Under our old ASA6 deployment, if you were to select the publisher under Users & Groups, or select the shortcut to your publisher under the SQL Remote folder in Sybase Central, you used to get a properties window that had a permissions tab where you could move between tables, views and procedures.
For the record, our publisher user is inherited from the public group.
What I've noticed is that if I try to view the permissions on our publisher under ASA6, we see a list of all of our available tables, views or procedures on that tab. Each permission is set as a "--", but my impression was the it was inheriting its permissions from public.
What I've noticed under SQL Anywhere 12, is that if you have selected your publisher (which in this instance is still inherited from public), and try to view table, view or procedure permissions, you get nothing in the list. I can add tables to the list by right clicking on the list and selecting tables (or views, or procedures), but I'm not sure if I'm doing something I don't need to do.
What I don't want to do is end up stepping on my permissions that are established by the public group.
Can somebody tell me if this is just way the UI works in Sybase Central 12 and that table, view or procedure permissions are invoked automatically from the public group?
Please advise if you need any clarification. TIA for any help.
asked 11 May '11, 18:12
In SA 12.0.1, permissions moved from the property sheet to the main Sybase Central window.
There was another change too. When viewing permissions for a user, previously all objects (tables, views and procedures) were listed regardless of whether they had any permissions set. Now, only objects with permissions set are shown. Note that I'm speaking of permissions that have been explicitly set for a user. (The permissions editors don't show permissions that are inherited through group membership).
So, it sounds to me like you don't have any permissions explicitly set for your publisher. If the publisher is a member of PUBLIC, then the publisher will inherit any permissions set for PUBLIC. However, you will have to select the PUBLIC group in the tree to view its permissions.
answered 12 May '11, 08:21