Re: Object Authority for SQL Use

Have more than one authority list...

Instead of PRODDATA have
ORDDATA
GLDATA
APDATA
ARDATA

However many groups that are required.

And you should have your users assigned to group profiles.

Group profiles are then given access via the authority list.

We have the group profiles/authority list cross reference. But the approach of having an authority list for each unique combination of users would be very problematic. We're long past the stage where our production data could be broken into just a couple dozen categories. For our E1 data libraries alone, I have dozens of users authorized to query only one/two/three files. Each time I added a new user for a new interface, I would further be breaking down the groups:
- MANDATA starts for manufacturing data,
- MANDTAJOBP gets broken off for an interface with a 3rd party scheduling software
- MANDTALAB needs some of the same files as MANDTAJOBP for an interface with lab software, but others as well. I'm now faced with an authority list for files that both Job Pack and the Lab software can use, another for the ones that just Job Pack can use, and a third for the ones that the Lab software needs. Oh wait, job pack needs to update one file, and the lab software another file, but neither one should have update rights to any other files.

I'll pass. I already have 160 authority lists for grouped library/library object authorities, and a total north of 220 counting all the TAA Tool ones.

_____________________________________________________________________
Spirax-Sarco Engineering Plc. This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.verizonbusiness.com/uk