ID Number: Q80830
1.11 4.20
OS/2
buglist1.11 buglist4.20
Summary:
Problem ID: PRSQL9202003
SYMPTOMS
When columns are added to an existing table with some columns
revoked of some permissions from a certain group, the permissions
extended to the newly added columns are not consistent. The group
will have the expected permissions on the first few columns in the
add list, but not on the rest of the columns.
CAUSE
When any columns are added to an existing table, the entries in the
sysprotects table corresponding to that table are not changed,
which is expected. However, when SQL Server uses this information
to calculate the permissions on a column for a group or user, the
results are not consistent and depend upon the position of the
columns when the columns are added.
WORKAROUND
This problem can be corrected by specifically granting or revoking
permissions on the newly added columns.
STATUS
Microsoft has confirmed this to be a problem in SQL Server versions
1.11 and 4.2. We are researching this problem and will post new
information here as it becomes available.
Additional reference words: 4.20