March 22, 2011 at 5:50 pm
Did a test in renaming the sa account. After renaming the account, I immediately run a test sql job which ended ok.
However a little while later (which is a few hours), i try to run the job. It failed with unable to access server. I figure out the problem. But why is there delay?
April 4, 2011 at 4:24 am
hi,
don'nt try to rename sa login, create the same privilage login as sa and disable the sa login.
u can do it by object explorer.
April 4, 2011 at 4:50 am
willtwc (3/22/2011)
Did a test in renaming the sa account. After renaming the account, I immediately run a test sql job which ended ok.However a little while later (which is a few hours), i try to run the job. It failed with unable to access server. I figure out the problem. But why is there delay?
You mentioned that you figured out what the problem was. What was the problem? Was it just that the job was still configured to run under the "sa" account?
Also, did you login as "sa" and change the name of the "sa" account? Maybe it was not able to apply the changes because you were still logged in as "sa"...
Thanks & Regards,
Nakul Vachhrajani.
http://nakulvachhrajani.com
Follow me on
Twitter: @sqltwins
April 4, 2011 at 4:44 pm
I had to run msdb.dbo.sp_sqlagent_notify to fix the jobs owned by sa.
April 4, 2011 at 11:09 pm
Please note that some other things can be broken by renaming the SA account. I have seen a number of people with failed SQL Server upgrades because of that. (Yes SPs have fixed some related issues, but I would advise against it as a normal practice.)
April 5, 2011 at 4:19 am
I would also advise against renaming the sa account. It is OK to disable this account, but as UMG Developer said some things (sometimes this includes a service pack install) break because the sa account is renamed.
If you disable the sa account then you achieve the security objective of preventing people from using this account. It is best practice to set up another account with sysadmin rights to do your DBA work with, and avoid using the sa account.
If you do decide to rename the sa account then you must also accept that some things may break and you are willing to accept these risks.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply