Arthur Fuller
fuller.artful at gmail.com
Sat Dec 20 06:13:24 CST 2008
In my experience, the most common application of this approach is in apps that involve web UIs. Even then, I don't recommend it because it's impossible to trace an anomoly to a specific user. But in terms of minimal work on the DBA's part, it does make sense. A. On Fri, Dec 19, 2008 at 4:41 PM, Dan Waters <dwaters at usinternet.com> wrote: > I was talking to a SQL DBA today at one of my customers. She suggested > that > I use a single username and password for all of the client PC's (about > 200). > I'm going to ask her about why we should do this in more detail later. I'm > setting up this BE with Windows Authentication. > > She threw me for a loop - why do this? Is this a standard practice in some > situation? My app at this customer has an entire virtual server and the > entire SQL instance is for just this app. > > Thanks! > Dan > > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > >