September 16, 2008 at 11:48 am
I'm new at a company, and no one seems to know the 'sa' password on Server_4 (2005) and Server_5 (also 2005). Server_1 (2000) has a linked server to Server_5 that was using 'sa', but someone here changed to "be made using the logins current security context". A linked server job bombed because of that, so I want to reset the 'sa' password on Server_5, and then use the 'sa' security context on Server_1 as it was before.
What can blow up by changing the 'sa' password ?? I realize any applications that have the password hardcoded will blow up, but does anything within SQL care if the password changes ? DTS, SSIS, Jobs ...
I know the 'sa' account is used much too freely here, and that is a problem for another day (soon), but I want to get the job working again.
September 16, 2008 at 11:50 am
Nothing should blow up AND you get to take care of those things that are using the SA account inappropriately all in one swift change. :w00t:
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
September 16, 2008 at 1:03 pm
Agree with David on this one. Nothing should blow up
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply