SQL Server 2005

All of a sudden we cannot log in using sa. The "enforce expiration"
option is not set.
How could this have happened outside of a user deliberately changing
the password? Can sa get
locked out for other reasons?

Bill E.
Hollywood, FL

"Bill E." <billmiami2 (AT) netscape (DOT) net> wrote

Not that I'm aware of.

Sounds like someone changed the sa password or you've got a bad case of
fat-fingering.

Worse case, I'd start looking for domain accounts and the like that didn't
exist before. (A typical 'first thing' a hacker would do.)




--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html

Thanks Greg.

This SQL Server is behind the firewall--not available outside the
corporate network. However, when I get a chance I'll follow your
suggestion.

Bill

"Bill E." <billmiami2 (AT) netscape (DOT) net> wrote

It's probably an innocent screw up then.

But you never know. (Besides, not all hackers come from outside a company
unfortunately.)




--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html

If the server authentication mode was changed to Windows
Authentication only sa would no longer work.

Roy Harvey
Beacon Falls, CT

On Tue, 11 Sep 2007 02:42:39 -0700, "Bill E."
<billmiami2 (AT) netscape (DOT) net> wrote:

No, it's still set to mixed mode and I'm using other logins for
applications.

Bill