January 24, 2014 at 5:54 am
Hi
I am about to disable the sa account on each server across our estate. We use mixed mode authentication (ideally for security we would just use windows authentication but this is not the case at present).
On the first server I am disabling the account I have checked the configuration manager and non of the services of running under sa.
There is one job 'syspolicy_purge_history' which is owned by sa - so I presume this would stop working and I would have to change the ownership of this job to an account with equivalent privilages ?
Apart from that I can't think what else might 'break' by disabling this account.
Is there any advice or lessons learned from anybody who has done this type of thing before ?
January 24, 2014 at 7:54 am
You can have SA as the job owner even if the account is disabled. Thats what I do
January 24, 2014 at 8:05 am
Hi
Yes I noticed that yesterday when I disabled the sa account on my test laptop and jobs still ran ( i had a ssis transaction log backup that i set to run every 15 mins).
Do I need to be concerned about other things stopping ? I am paranoid about disabling the account on the Production system!!
January 24, 2014 at 9:36 am
I would check any config files your app has for sure, if anything uses the sa account for things like that then they will stop.
Internal objects owned by SA should be fine. Linked servers will fail though.
January 24, 2014 at 3:03 pm
When you say linked servers will fail ? I presume you mean if they are configured to use sa as the login account - which ours are not !
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply