Hi...
I have an application role in "Database A" which I am able to connect to without any problems..... until now:
Database A has a view which is in Database B. When I try to access this view, I get a permission denied error.
So, the obvious question is:
After I execute the sp_setapprole command, how can I access the view which reads from Database B?
Thanks,
Forch
Hi!fact: sp_setapprole can't be invoked from within a stored procedure
scenario: my users are validated in the database! I have a Users table that contains user related information, incl. passwords and profiles.
Actually users login through an applicational SP -- svc_login @username, @password -- and all users have the same permissions.
desired scenario:Have 1 app. role per user's role; once the user log in through the svc_login, I would like to change his appl. role based on his profile.
I already saw that i can't do this at DB side! Is there any known alternative to this kind of scenarios? Or must I rely on the front-end application and share the role password with it?Thanks in advancejmn
Hi All,
Is there any limitation for setting password to an approle (like it should be 8 character long, should not start with numbers) ?
If so, what are those limitations ?
Does the same is applicable for sp_setapprole which uses the same password ?
please confirm, for both SQL Server 2000 and 2005 versions.
thanks in advance,
Regards,
Kailai
Does anyone know if this is a SQL Native Client bug? I've read a previous thread (posted back on Jan. 18th, 2007) about this error, but there are no replies. I am getting this error when I issue the sp_setapprole command using sqlexecdirect() ODBC api call. Is there any way to work around this? Or is there a fix to the SQL Native Client? The error 15002 message text states "The procedure sys.sp_setapprole cannot be executed within a transaction". This is on a new connection so there should be no transactions active at the time. Thanks in advance for any info anyone can provide on this.
View 5 Replies View Related