I have a problem that seems to be a bug in SQL Server. We
have a database that is in merge replication with 5
subscribers. The platform is SQL Server 2000 SP3a running
on Windows 2000 Server SP4.

The problem occurs in tables where columns are added
through the publication. We added a column by going to
the publication properties -> Filter Columns -> select
appropriate table -> click Add Column to Table. This is
done with replication up & running. The column is created
and pushed to subscribers with no problem.

The problem occurs when I try to set the permissions for
the newly added column. I have been unable to control the
permissions on the column either through the management
console or via the GRANT command in a query analyzer
window. In addition, I backed up and restored the
production database onto test server with no replication.
I was still unable to control permissions on the column
added through the publication. Also, I added another
column manually to the affected table and was unable to
control permissions on that column either. I went to
another table in the same database and was able to add
columns and control permissions with no problem. The only
problems were encountered with tables where columns had
been added through the publication, and only to columns
added through the publication (or columns added after
that action).

Everything appears to execute normally when attempting to
modify permissions via either MMC or GRANT command.
However, when I re-enter the Manage Permissions
interface, the permissions I assigned to the added
columns are not there. In several tests, I would change
the permissions on a several columns at the same time.
Some of the columns had been added while others were
original columns. When I re-entered the Manage
Permissions interface, only the permissions I assigned to
the original columns had remained. An attempt to make an
update to the table verified that the permissions were
not set for the added columns.

Does anyone have any ideas? I have a user in one of the
subscriber locations that needs update access to the new

In my experience, enterprise manager doesn't always report these column level security settings correctly. Have a look at doing the same thing in stored procs. I have just tested this by adding a column called newcol to my publication and allowing joe to see it. When I use the interface to add permissions, the new column permissions are not visible when reentering. Same thing for using grant select on region(newcol) to joe. However, the permission has been registered as reported by sp_protect

exec sp_helprotect 'region

Testing these permissions in QA shows that sp_helprotect returns the correct values

HTH