SA password-cracking-vulnerability warning-the black bar safety net

2007-05-05T00:00:00
ID MYHACK58:62200715344
Type myhack58
Reporter 佚名
Modified 2007-05-05T00:00:00

Description

0)off of your existing database service. 1)Create a new instance, is to reinstall a sql server, hereinafter referred to as the new 2 put your old database instance, hereinafter referred to as the old the master. mdf , master. ldf copy to a folder 3) in the new, by attach the db the way to put in the folder the two files added for the new database, of course, name and location in the Add when they are going to change. 4 in the new, by a statement of the way, put the master in the table sysxlogins in the sa password to update to your just added the database to the old of the master of the table sysxlogins in the corresponding sa in the Password field. 5 put your just add the database to the old master in the new detachdb, then put the file overwrite the old corresponding file covering the front of the file backup 6 restart the old server, to see whether it is feasible 7 uninstall new server

http://www.mssqlcity.com/FAQ/Trouble/error_259.htm http://www.mssqlcity.com/FAQ/Devel/AmendSysTb.htm

How can I resolve the error 2 5 9? Answer: This is the error 2 5 9 message text: -------------------------------------------------------------------------------- Ad hoc updates to system catalogs are not enabled. The system administrator must reconfigure SQL Server to allow this. -------------------------------------------------------------------------------- You will get the error 2 5 9 when you tried to modify the system catalogs directly while the allow updates system configuration option is set to 0. To work around the error 2 5 9, you should set the allow updates option to 1 by using the sp_configure system stored procedure. Check this link for more details: How can I edit the system tables manually? -------------------------------------------------------------------------------- Answer:

It is not recommended to do, but it is possible. You should set the allow updates option to 1 by using the sp_configure system stored procedure.

This is the example:

sp_configure 'allow updates', 1 GO RECONFIGURE WITH OVERRIDE GO

Read about the sp_configure system stored procedure in SQL Server Books Online

Code: -------------------------------------------------------------------------------- sp_configure 'allow updates', 1 GO RECONFIGURE WITH OVERRIDE GO -------------------------------------------------------------------------------- use master_old update sysxlogins set password=NULL where name='sa' select name,password from sysxlogins