MS SQL Server, Strange behaviour of is_member() in SQL-Server 2000 (Product Version 8.00.534, S

Strange behaviour of is_member() in SQL-Server 2000 (Product Version 8.00.534, S

Author	Message
Daniel Walzenbac #1 / 2	Strange behaviour of is_member() in SQL-Server 2000 (Product Version 8.00.534, S I have a couple of users in my database which belong to specific roles. Unfortunately, is_member('roleXY') returns 0 for some users although they belong to this role. I know that there is a fix for the SQL Server 7.0 regarding to a similar problem (FIX: Execution of IS_MEMBER May Cause AV When Many Roles Exist [Q246189]) FROM MSDN************ BUG #: 56457 (SQLBUG_70) BUG #: 56457 (SQLBUG_70) Symptoms When many roles exist in a database, and you use the IS_MEMBER() T-SQL function to determine if the current user is a member of a particular role, you may receive an error similar to the following: ODBC: Msg 0, Level 19, State1 SqlDumpExceptionHandler: Process 8 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. Use IS_SRVROLEMEMBER('role') instead. Refer to SQL Server Books Online for specifics on the use and syntax of this function. **************** Is this problem also known in SQL Server 2000 since I sometimes get similar error messages. Any help is greatly appreciated. Thanks in advance. Daniel Walzenbach
Sat, 09 Apr 2005 15:47:13 GMT

Jon Waddingt #2 / 2	Strange behaviour of is_member() in SQL-Server 2000 (Product Version 8.00.534, S I have been researching the same thing. What I found is that if your user is also part of a server role such as System Administrator, IS_MEMBER does not return the correct value. If you use sp_helprolemember 'roleXY' the MemberName column returns the correct list. Go figure... Quote: > I have a couple of users in my database which belong to > specific roles. Unfortunately, is_member('roleXY') returns > 0 for some users although they belong to this role. > I know that there is a fix for the SQL Server 7.0 > regarding to a similar problem (FIX: Execution of > IS_MEMBER May Cause AV When Many Roles Exist [Q246189]) > FROM MSDN************ > BUG #: 56457 (SQLBUG_70) BUG #: 56457 (SQLBUG_70) > Symptoms > When many roles exist in a database, and you use the > IS_MEMBER() T-SQL function to determine if the current > user is a member of a particular role, you may receive an > error similar to the following: > ODBC: Msg 0, Level 19, State1 SqlDumpExceptionHandler: > Process 8 generated fatal exception c0000005 > EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this > process. > Use IS_SRVROLEMEMBER('role') instead. Refer to SQL Server > Books Online for specifics on the use and syntax of this > function. > **************** > Is this problem also known in SQL Server 2000 since I > sometimes get similar error messages. > Any help is greatly appreciated. Thanks in advance. > Daniel Walzenbach
Wed, 13 Apr 2005 00:38:32 GMT

Page 1 of 1

[ 2 post ]