BUG: Permissions Granted Improperly on New Columns

ID: Q80830

The information in this article applies to:

BUG# OS/2: 1225 (4.2)
       NT:  891 (4.2)

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 version 4.2 for OS/2 and Microsoft SQL Server version 4.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. 


Keywords          : kbother kbbug4.20 SSrvServer SSrvWinNT 
Version           : 4.2 | 4.2
Platform          : OS/2 WINDOWS 
Issue type        :

Last Reviewed: March 17, 1999