Alan Bourke <> wrote:
> Stephen the Cook wrote:
>> 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. B
>
> If people were changing servers the whole time it would be, but in
> real terms how likely is that?
Changing servers? Depends on the shop. Getting more servers, buying other
companies that suddenly come under your control? Priceless
> If you do it properly you have one encrypted connection string in a
> config file that you need to change.
And one for reporting in a read only manner. A secret backup that is there
in case someone goofs up the sa account. I could go on.
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/703 - Release Date: 2/26/2007
2:56 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.
