The biggest change is that with integrated security, the ONLY way for a user
to connect to a SQL Server is via an approved OS account. Along the same
lines, this means that only named pipes and/or multi-protocol can be used as
your network protocol.
As for user rights in different databases, nothing really changes. The
integrated / mixed / standard security models are only about logging on to
SQL Server - ie., which SQL login do I get? The security models do not
affect how you map an SQL Login to a database user or group. You still
associate SQL Logins with database users and groups in the different
databases, and grant object and database permissions to those users and
groups, just like with standard security.
There's my .02 worth. Hope it helps!
--
Chris Leonard
SQL Server / Windows NT MCP
>Hello,
>Currently our company is using SQL Server 6.5 independent SQL Security
>model, where each user has a logon ID. We are thinking of implementing
>the SQL Integrated Security model to rid of the logon required for each
>users. What are some of the issues I should be aware of if I change my
>SQL Server 6.5 to use the integrated security model? Also if I change
>to integrated security model, how do user rights play a role on
>different databases?
>If someone can shed some light on this topic...
>Thank you,
>-atif-
>Atif *
>Systems Engineer
>Strategic Network Designs, Inc.
by