Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In our server application we use single account to access to the SQL Server. We used to use SQL Authentication. Now we are thinking to remove credentials from config files; and one of the solutions is to use Windows Authentication.

We are mostly concerned about performance. Is there any differences?

Another problem, is domain controller that occasionally could be down. Is SQL will be able authenticate in this case?

What do you think?

share|improve this question
up vote 2 down vote accepted

You shouldn't see any noticeable performance issues, assuming that all is well with your network and domain. You'll most likely see impersonation / delegation problems before you start seeing performance issues.

share|improve this answer
Thatnks, yet another question. What will be in case domain controller is down? Application will not be able to connect? Does SQL server cache something? – Mike Chaliy Jan 18 '10 at 17:03
It's possible that your app won't be able to connect, but it will depend on when access tokens are created for the app process. If you only have one domain controller and it goes down you'll have bigger problems than just your app's authentication, though. – squillman Jan 18 '10 at 17:23

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.