As we all know, in M $ SQL, there is an account sa that is definitely a hidden danger in network security. by default, it is assigned to the fixed server role sysadmin, it cannot be changed.
As we all know, in M $ SQL, there is an account sa that is definitely a hidden danger in network security. by default, it is assigned to the fixed server role sysadmin, it cannot be changed.
Generally, this sa cannot change or delete the name. it is a little tasteless. After installing sql2000, I felt strange. I was always worried that my computer would not be able to pull out my password one day, even in the dark road for so many days, if it is passed out, it will damage the face. Maybe you can say that you have a strong password. this method is feasible, but it is not a long-lived record. The so-called grass to be rooted, if you delete sa, you don't have to worry about brute-force cracking.
Hehe: Well, it may be because you have been reading this nonsense for a long time, let's take the sa to unload the eight blocks. first open the Enterprise Manager in SQL, select the SQL server configuration attributes in the Tools tab, and click server settings, are you allowed to directly modify the front box of the system directory? click it.
Open the query analyzer and log on to the analyzer (haha, whatever account you use, but you must have the db_owner permission in the master database ).
Update sysxlogins set name = 'the name you want to change to 'where sid = 0x01
Update sysxlogins set sid = 0xE765555BD44F054F89CD0076A06EA823 where name = 'name you want to change to name'
, OK, the execution is successful, good pull, switch to the Enterprise Manager and refresh the login in security to see if sa is changed to xwq pull. haha, right click xwq, is there any option for pulling and deleting. Check if sa has not been pulled.
Postscript
How to Delete sa directly in the query analyzer
The method of deleting sa directly in the query analyzer is similar to that mentioned above, but this time it is not in the enterprise manager, instead, SQL provides us with powerful stored procedures to complete this task. The following describes the stored procedure sp_configure and sp_configure to be used to display or change the global configuration settings of the current server.
Its syntax:
Sp_configure [[@ configname =] 'name']
[, [@ Configvalue =] 'value']
Instance:
Sp_configure 'allow updates', 1
Go
RECONFIGURE WITH OVERRIDE
Go
Good pull, so that we can update the system table pull. next we will pull the update sysxlogins set name = 'you want to change to the name 'Where sid = 0x01, then delete "the name you renamed"
However, note that the execution permission without parameters (or only the first parameter) on sp_configure is granted to all users by default. Execution permission of sp_configure with two parameters (used to change configuration options) is granted to sysadmin and serveradmin fixed server roles by default. RECONFIGURE permissions are granted by default to sysadmin fixed server roles and serveradmin fixed server roles, and cannot be transferred. It must also be db_owner in the master.
