![]() ![]() ![]() ![]() Certainly stops you looking an idiot in managements eyes for having to reboot production because you have locked yourself out! It is often a good idea to have a separate site security officer, just to get you out of this sticky situation. If you have a user with sso_role enabled, login with that account and change the 'sa' password that way. I just tried the above method and it works fine. It failed for me and I had to kill the dataserver and get a new password. Take it from me that the risk is not worth it. I thought that setting it to null would be enough, and exited isql thinking that I would be able to get in with a null password. You must rememeber to reset the password before exiting isql or sqsh. Update syslogins set password=null where name = 'sa' Sp_configure "allow updates to system tables",1 If you see that someone is logged using the 'sa' account or is using an account with 'sa_role' enabled, then you can do the following: Funnily enough, this is obviously what Sybase think because it is one of the questions in the certification exams. If you have more than one person accessing the server using the 'sa' account, consider using sa_role enabled accounts and disabling the 'sa' account. I know that most people use the 'sa' account all of the time, which is fine if there is only ever one dba administering the system. Remember Douglas Adams famous quote "Don't panic" is the first thing! More DBA job interview questions and answers at We have lost the sa password, what can we do? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |