PRB: SQL Security Manager Changes Not Moved to Secondary Node

ID: Q193993

The information in this article applies to:

SYMPTOMS

By default, the SQL Security Manager does not propagate security permission changes to secondary nodes on a cluster installation.


WORKAROUND

Perform the following steps to work around this problem:

  1. Start the Cluster Manager utility.


  2. Select the appropriate group containing the SQL Server service.


  3. Select the Vserver, right-click Generic Service, and then click Properties on the shortcut menu.


  4. Click the Registry Replication tab.


  5. Click Add.


  6. Add the following registry key:

    HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLSERVER


Adding the registry key causes the registry changes to replicate to the other node, which resolves the issue.

Additional query words: prodsql xp_grantlogin, xp_revokelogin 


Keywords          : 
Version           : WINNT:6.5
Platform          : winnt 
Issue type        : kbprb

Last Reviewed: April 19, 1999