Home Forums SQLServerCentral.com Editorials SQL Server Authenticated Users, why are we still using them? RE: SQL Server Authenticated Users, why are we still using them?

  • March 30, 2018 at 7:52 am

    #1985073

    BobAtDBS - Friday, March 30, 2018 7:20 AM

    I see your point if you live in a world where all your users are part of your domain.  But if you serve up applications that connect to SQL Server from hundreds (in our case thousands) of users who are NOT in your domain, you have two choices.  Use SQL Server authentication, or use one (or a few) logins and do your own login and password control, which may or may not be as good or better than what SQL Server offers.  I'm open to viewpoints!

    I am assuming that if you have thousands of users you are talking about a web app?  If you are, normally websites running under IIS will have their own application pool.  You can set the identity of the application pool to be a network user.  Normally, we get our AD guys to create a service account, then all access to the web app happen through this one AD account.

    Ben