Re: SQL Logins vs Windows Authentication
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Thu, 20 Sep 2007 22:05:40 +0000 (UTC)
Richard Mueller [MVP] (rlmueller-nospam@xxxxxxxxxxxxxxxxxxxx) writes:
I assume it would not be the domain the hosting company uses for their
normal business, but a domain they created for the hosted customers. I
don't know how the customers will make the connection, but they will
login to the Active Directory domain. They will use one of several
application servers where they would launch several applications,
including mine. I assume the SQL Server is in the same domain.
As Roy said, that may be the catch.
If the SQL Server machine is in your customer domain, I guess that will
make administration more difficult for the hosting company.
But if the SQL Server machine is in your customer domain, I see no
reason why you should not be permitted to use Windows authentication.
It seems to me if SQL Logins are used, either all customers use the same
SQL credentials, or I read the credentials from text files. Why have
passwords in that case?
You have to descend to give them login window and a personal SQL login
and password to log in with. This would be needed for auditing etc.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- SQL Logins vs Windows Authentication
- From: Richard Mueller [MVP]
- Re: SQL Logins vs Windows Authentication
- From: Erland Sommarskog
- Re: SQL Logins vs Windows Authentication
- From: Richard Mueller [MVP]
- SQL Logins vs Windows Authentication
- Prev by Date: Re: SQL Logins vs Windows Authentication
- Next by Date: Re: drop a database user. assign objects to dbo.
- Previous by thread: Re: SQL Logins vs Windows Authentication
- Next by thread: Re: drop a database user. assign objects to dbo.
- Index(es):
Relevant Pages
|
|
