Monday, March 26, 2012

Problems with SA Password

Hello, we have some problems because some malicious user change the SA
password from my SQL Server 2000, how can i restore it or fix this problem?
Thanks for the help.Look up sp_password in Books Online. Connect using Windows authentication,
with a local/domain admin account...
http://www.aspfaq.com/
(Reverse address to reply.)
"egsdar" <egsdar@.discussions.microsoft.com> wrote in message
news:6295768F-DD03-4BE8-85B0-2AD41D37AFA2@.microsoft.com...
> Hello, we have some problems because some malicious user change the SA
> password from my SQL Server 2000, how can i restore it or fix this
problem?
> Thanks for the help.|||Here are three options (in order of preference).
1. Use another user account that has sysadmin priveliges in SQL Server to
change the password back. (sp_password)
2. Restore the master database from backup.
3. Reinstall the master database, then reattach all of your databases and
rebuild your sql logins.
4. Pay someone lots of money to hax0rx your system.
Rick Sawtell
MCT, MCSD, MCDBA
"egsdar" <egsdar@.discussions.microsoft.com> wrote in message
news:6295768F-DD03-4BE8-85B0-2AD41D37AFA2@.microsoft.com...
> Hello, we have some problems because some malicious user change the SA
> password from my SQL Server 2000, how can i restore it or fix this
> problem?
> Thanks for the help.|||I would call Microsoft Product Support before doing #4
Keith
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:uxxxYcRwEHA.536@.TK2MSFTNGP11.phx.gbl...
> Here are three options (in order of preference).
> 1. Use another user account that has sysadmin priveliges in SQL Server to
> change the password back. (sp_password)
> 2. Restore the master database from backup.
> 3. Reinstall the master database, then reattach all of your databases and
> rebuild your sql logins.
> 4. Pay someone lots of money to hax0rx your system.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
> "egsdar" <egsdar@.discussions.microsoft.com> wrote in message
> news:6295768F-DD03-4BE8-85B0-2AD41D37AFA2@.microsoft.com...
>|||log in with a windows administrator account and try connecting to sql with
Windows Authentication. It SHOULD work (if you have not removed account to
the BUILTIN\administrator account in sql).
Sasan Saidi, MSc in CS
Senior DBA
Brascan Business Services
"I saw it work in a cartoon once so I am pretty sure I can do it."
"egsdar" wrote:

> Hello, we have some problems because some malicious user change the SA
> password from my SQL Server 2000, how can i restore it or fix this problem
?
> Thanks for the help.|||Everyone else's solutions will work but here is one more you can use.
Stop the MSSQL service on the system you are having trouble with.
Copy the master.mdf and mastlog.ldf files somewhere safe.
Then copy these same files to another server with the same service pack and
hotfix level, like a dev box, and place the files in a DIFFERENT directory
other than the system directory where that installation's master database
files are located.
Execute the sp_attach_db command using these files but assign a different
database name to it.
Once online, you can edit the sysxlogins table in that database and set the
password field to NULL for the sa account--id = 1.
Execute sp_detach_db to remove this database from this system and copy both
the master.mdf and mastlog.ldf files back to the original server.
Restart the MSSQL service on the failed server.
You should now be able to reconnect to your server using the sa account and
NULL password, which, I suspect, was the original configuration.
Now, before you do anything else...CHANGE THE SA ACCOUNT PASSWORD AND NEVER,
NEVER, NEVER, NEVER share it with anyone other than the Database
Administration staff.
Sincerely,
Anthony Thomas
"Aaron [SQL Server MVP]" wrote:

> Look up sp_password in Books Online. Connect using Windows authentication
,
> with a local/domain admin account...
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "egsdar" <egsdar@.discussions.microsoft.com> wrote in message
> news:6295768F-DD03-4BE8-85B0-2AD41D37AFA2@.microsoft.com...
> problem?
>
>sql

No comments:

Post a Comment