SQL 2000 sa password

Dear All

Im planning to change my sa password, but there are alot of automated jobs related to sa account, once i changed it the jobs are unble to start, i have change the login for those jobs but still some jobs can not start..

Please I want to change my sa password and do the required changes for all this jobs.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Duane LawrenceCommented:
Create a new account but try to give it less than sa privelges.  Move your processes over to the new account one by one.  Make sure one works before moving the next.  This will take a long time, but on a live database it is better.  After all processes are off of the SA account, you can change it at will.

I will apoligize first, but I just can't help myself from saying this.
I have seen a SQL Server admin T-Shirt that makes a joke of doing this, it comes from the Microsoft SQL Server World Wide User Group (sponsored by Microsoft).  

Melih SARICAOwnerCommented:
u can try this

-- start Of Stement

declare @Jobname varchar(255)
declare @NewOwner varchar(50)

set @NewOwner = 'Non_Zero'

declare mCursor Cursor for
      select [name] from msdb..sysjobs
open mCursor
fetch Next from Mcursor into @JobName
While @@fetch_status = 0
   exec msdb..sp_update_job @job_name = @JobName
          , @owner_login_name = @NewOwner
      fetch Next from Mcursor into @JobName

-- End Of Stement



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Amen to DuaneLawrence.

Never setup production jobs to use the sa password. sa is just too powerful and programmers can totally ruin the database all too easily. I should know, 'cause I'm one of 'em. Though I have never screwed up a procduction database messed up by a programmer, I've come real close, and I've had to help recover from such messes more times than I can recall.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.