July 30, 2004 at 2:59 am
I have two databases, say A (OLTP) and B (reporting), on the same 2K server.
I need to run stored procedures in A that reference and populate data in B
I know the role but not the user id (which cannot be predicted) of the user in A. That role does not and cannot have system privileges. I do not know the user id beforehand and so cannot grant it any privileges in advance.
The process must be triggered from A.
The only way that I have been able to think of is to grant the necessary permissions to the Guest account in B but that, while just tolerable, is not exactly secure!
I would welcome any alternative suggestions.
July 30, 2004 at 5:08 am
I would create an NT Group and assign any/all the users that MIGHT potentially do this to the NT group. Then assign the appropriate permissions to the NT group and you should be good to go
Good Hunting!
AJ Ahrens
webmaster@kritter.net
July 30, 2004 at 7:35 am
I'd create a role in B and assign that permissions. Then if you can use an NT group with both roles, do that. If not, add everyone with the role in A, to the role in B.
July 30, 2004 at 7:42 am
Good ideas. Unfortunately, it is using SQL security and the application's security creates user ids 'on the fly' and throws them away when the user logs out. I have no way of knowing in advance what they will be! A possible solution would be to modify the front end security but that would be expensive in scarce resource to do it and in the regression testing required in a very sensitive area.
August 2, 2004 at 12:24 am
Why is the application security designed to create users and throw them away?
August 2, 2004 at 3:04 am
Good question! Not my design.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply