BUG: sp_helprotect May Give Redundant InformationLast reviewed: May 5, 1997Article ID: Q93341 |
The information in this article applies to:
NT: 879 (4.2) SYMPTOMSThe results of executing the system stored procedure, sp_helprotect, on a table with more than 100 columns will indicate that the users who have been granted "delete" permission on the table, have "delete" permission on the table as well as "delete" permission on the columns beyond column 100. For instance, sp_helprotect "mytable" will give the following results, where "mytable" is a 101 column table, with the 101st column named as c1. Note that "delete" permission on the table has been granted to the group "public".
Type Action User Column ----------------------------- Grant Delete public all Grant Delete public c1In the above results, the second row is redundant. Note that if there are 102 columns in the table, there would be an extra row in the results. The same redundant behavior is seen for the insert permissions granted to users.
WORKAROUNDIgnore the superfluous rows. For actions like "delete" and "insert", the only valid rows from sp_helprotect are those where the "column" information is "all".
STATUSMicrosoft has confirmed this to be a problem in SQL Server version 4.2 for OS/2 and Microsoft SQL Server versions 4.21 and 4.21a. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional query words:
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |