Using SQL Server AD Service Account With Applications


  • Trying to understand the reason why we should have a dedicated SQL server AD account and should not be used for any other purpose which includes not using it with connection strings in the .net application configuration files. Sure, the password is not shown in the config files if integrated security is used. However, the only reason I can think of is when troubleshooting issues with the sql server, if we have to trace anything for the specific application user, then, we may have additional work of filtering the logs. What else could be reason why we should NOT use SQL server AD account in the application config files?

    Will greatly appreciate your quick input.




    Wednesday, May 2, 2018 5:10 PM

All replies