Integrated windows NT security

[Ajay]

Hi All,

Can we implement a table level (object) security on the groups of the windows NT domain using the integrated windows NT security so that one group has
the permission over one table to update ,select ,delete the information and other group has permission has for some other table.

Thanks
Ajay

[Tom Mack, MCSE]

NT Security is integrated with SQL security on a user-by-user basis. By that, you can't used NT-based groups to define SQL-based groups. Also, be carefull in assigning your group structure if you are new to SQL security. In NT, a user can be a member of as many groups as you have. In SQL a user can only be a member of two groups, and one of those has to be "Public".

Tom Mack


------------
Ajay at 4/7/99 1:39:47 PM

Hi All,

Can we implement a table level (object) security on the groups of the windows NT domain using the integrated windows NT security so that one group has
the permission over one table to update ,select ,delete the information and other group has permission has for some other table.

Thanks
Ajay

[Dano]

One of our development boxes has an authentication issue.

When domain users try to connect using NT Authentication,
users get the following error:

Cannot Generate SSPI Context.

SQL Service account is running as a domain account.
The NT Group has been granted login permissions

Any suggestions?

[Sivakumar]

The error "Cannot general SSPI context" may occur during an operation such as rebuilding or populating a Full-Text Catalog. This error occurs when an invalid Service Principal Name (SPN) prevents MSSearch from making an OLE DB connection to SQL Server.

Resolve this error by finding and deleting the invalid SPN using the SetSPN utility from the Windows 2000 Resource Kit. Alternatively, stop and then start the SQL Server service on the local server.

To list the current registered SPNs, type the following from a command prompt:

Setspn -l SQLServerName

To delete the invalid SPN, type the following from a command prompt:

Setspn -d SPN


Note :The value for the SQLServerName parameter can be either the server name if it is running under LocalSystem, or the service account name without a domain qualifier.


For more information about the SetSPN utility, see the Windows 2000 Resource Kit documentation.


Got the above info from SQL Server Books Online

HTH,

Regards,
Sivakumar


------------
Dano at 1/4/2002 9:23:48 AM

One of our development boxes has an authentication issue.

When domain users try to connect using NT Authentication,
users get the following error:

Cannot Generate SSPI Context.

SQL Service account is running as a domain account.
The NT Group has been granted login permissions

Any suggestions?