I actually prefer to run in Windows Only mode. I do switch down to mixed mode when I have to, though
(typically some darn app that doesn't support Windows login or Windows login cannot be used because
of firewall/domain reasons).

Signature
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
> Gurus,
>
> Is there any disadvantage to running a SQL Server in Windows Authentication mode only?
>
> --
> Spin
Spin - 16 Mar 2008 13:40 GMT
>I actually prefer to run in Windows Only mode. I do switch down to mixed
>mode when I have to, though (typically some darn app that doesn't support
>Windows login or Windows login cannot be used because of firewall/domain
>reasons).
Thanks TIbor. What makes you prefer to run in Windows Only mode?
Tibor Karaszi - 16 Mar 2008 17:42 GMT
> Thanks TIbor. What makes you prefer to run in Windows Only mode?
One more set of accounts that cannot be used. I.e., even though SQL logins can exist when SQL Server
run in Windows Only mode, nobody can login using a SQL Server login. And since we've only recently
have the ability to specify password aging, complexity rules etc for SQL logins, I prefer if it
isn't possible to login at all using SQL logins - if the surroindings allow this.
Just imagne the nimber if times I've heard, when consuting "Yo! You have the password to sa?". ;-)

Signature
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
>>I actually prefer to run in Windows Only mode. I do switch down to mixed mode when I have to,
>>though (typically some darn app that doesn't support Windows login or Windows login cannot be used
>>because of firewall/domain reasons).
>
> Thanks TIbor. What makes you prefer to run in Windows Only mode?
anxcomp - 17 Mar 2008 00:18 GMT
Hello,
> I actually prefer to run in Windows Only mode. I do switch down to mixed mode when I have to, though
But what in bellow situation:
Two active directory domains CompanyA.local (NetworkA) and CompanyB.local
(NetworkB).
NetworkA and NetworkB connected by VPN.
NetworkA:
srvsql.CompanyA.local
NetworkB:
srvsql.CompanyB.local
All ports open between srvsql.CompanyA.local and srvsql.CompanyB.local, no
firewall.
I have DOMAIN ADMIN account on each domain CompanyA\me, CompanyB\me,
unfortunately I can't connect to srvsql.CompanyB.local from
srvsql.CompanyA.local by WindowsAuthentication, I'm using SQl Logins and this
works.
How use WindowsAuthentication in this situation, where is the problem?

Signature
Regards,
anxcomp
I can think of one, because I have been limited by it before: consultants
cannot connect to the database with their laptop's, which in my case has 10+
years of acquired tools, scripts and knowledge stored on it. And no, I will
not ever connect my laptop up to another's domain.

Signature
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
> Gurus,
>
[quoted text clipped - 3 lines]
> --
> Spin
Tibor Karaszi - 19 Mar 2008 08:52 GMT
Good point, Kevin! I also recognize me so very more productive when I can work from my own machine
against customer instances.

Signature
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
>I can think of one, because I have been limited by it before: consultants cannot connect to the
>database with their laptop's, which in my case has 10+ years of acquired tools, scripts and
[quoted text clipped - 6 lines]
>> --
>> Spin