Derek Kalweit <> wrote:
> Yes-- windows authentication needs a valid windows account. Accessing
> locally, that can be a local account-- in a network environment, that
> must be a domain account, an account on a trusted domain, etc.
>
> Simply put, windows authentication is usually a pain in the a$$
> unless you already have a domain setup. I almost always use sql auth
> instead of windows integrated... As for security, any MSSQL traffic
> should only be done over a secured network connection(lan, VPN, etc.)
> anyways.
I'm sorry but this advise is poor for any system. From the SQL2000 days and
now in the more secure SQL2005 days security within the domain is what you
want to use. Sure you can use straight SQL Auth, but it's a RPITA when you
ever change servers. Been there and done that, have the t-shirt for grins.
Stephen Russell
DBA / .Net Developer
Memphis TN 38115
901.246-0159
"A good way to judge people is by observing how they treat those who
can do them absolutely no good." ---Unknown
http://spaces.msn.com/members/srussell/
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.4/702 - Release Date: 2/25/2007
3:16 PM
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
