FIX: Execution of IS_MEMBER May Cause AV When Many Roles Exist

This article was previously published under Q246189
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 56457 (SQLBUG_70)
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, State1SqlDumpExceptionHandler: 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.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
This will not happen when you check every role for membership. For instance, it may appear when you check for membership in the 100th role but the first 99 will check fine.

Article ID: 246189 - Last Review: 10/22/2013 02:35:29 - Revision: 2.1

Microsoft SQL Server 7.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix KB246189