This content has been marked as final. Show 2 replies
1 of 1 people found this helpful
Here is some information from some of the SD Experts hope this helps:
- Almost all of our system testing is done using Windows authentication. Almost all testing done by Support is SQL so you’ve definitely got nothing to worry about.
- Our high security customers use Windows Authentication.
- The great thing about Windows Authentication is you can grant rights privileges based on your AD credentials which is typically more secure than a single SQL Server authentication account. However, now rights are bound to individual users which means that if you wanted to stand up a web service, for example, that accesses the database remotely on another server, you need to use an individual’s AD account which also means they need to login to the server where the web service resides since it will use the windows credentials from whomever is logged in.
- The nice thing about SQL Server Authentication is you can create one account, give privileges, and can log in anywhere as long as you’re using the SQL Server account credentials independent of whomever is logged into the server where your service is running. However, this is not as secure since if the account credentials were ever compromised the single account credentials would need to be reset which means ALL sql connection strings would need to be updated in all of your services.
Sounds like there are bonuses for both for sure.