Logging in as SQL's "sa" Fails on the First Attempt but Not on the Second
Posted on 2016-08-13
This experience that I had, yesterday, simply peaked my curiosity. So, I thought that I would ask you all.
Yesterday, our DBA changed a SQL instance's "sa" password.
In addition, we have an app that utilizes an ODBC connection to connect to this SQL instance. The ODBC connection, though, was not configured with "sa" as the user ID.
In any case, we have this app installed on three Terminal Server boxes.
After this password change, I attempted to login to the app as "sa" on all three boxes.
The very first attempt on each box failed but not the second.
True, it's possible that I may have simply typed the new password incorrectly, during the first attempt on each box.
But, I'm not so sure that that's the case. It just really seems odd to me that, after an "sa" password change, the first attempt on three Terminal Server boxes fails but not on the second attempt.
This seems more than just a simple case of a mistyped password or coincidence. Again, though, what do you all think?