SQL sa password renew issue

So it turns out I have an old password on my 2005 SQL server that does not meed the current Domain password requirements.  I have not renewed it yet as it is running my production database.  I am also in the middle of bringing up a new test production database server at a different site we'll be moving to in a few months.  The sa password on the SQL 2014 instance is sufficient to meet the domain password requirements.  Obviously both passwords are different.  I believe this password is keeping me from connecting to my new db on the new server.  I can think of two options but will need some guidance.

1.  I can set the existing 2005 sa password to the same as the 2014 sa password on the new server.  Question is, will that kill my existing db or can I just set the password and stop/restart and all is good?

2.  I can set my login to the same User Mappings as the 2005 sa logon and make the same changes to my 2014 logon.  I think this on is more work and error prone than the first?

Once I do either of these I will need to do another 2005 db backup of all the databases then copy and restore them to the 2014 instances.

Am I missing anything?
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.

gibneytAuthor Commented:
Actually  I just noticed the "Enforce password policy" box.  I unchecked it and was able to set the 2014 sa password to match the 2005 sa password.  Problem is I still get the "Connection could not be established" error when I try to bring my new db client online.

I did check that I can login to the 2014 sa account using the osql command line and get the "1>" prompt when successful.

In the SQL 2005 environment  there was a single instance with all dbs contained.  in the SQL 2014 environment I have several instances so that I can separate the processes of the live and test dbs.  the live instance will have the software's db as well as the company db.  The test instance will only have a copy of the company db.

Still, am I missing anything?


Brian CroweDatabase AdministratorCommented:
Best Practice: DISABLE the "sa" login (It's one of the first actions I take after creating a new SQL Server Instance)

I don't know the purpose of the database but if it is used for any production purposes then you should try to enforce a policy of least privilege.

Be careful with multiple SQL Server instances on the same machine.  SQL Server will, over time depending on usage, stake out and claim all available memory unless you set a maximum.

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
Vitor MontalvãoMSSQL Senior EngineerCommented:
"Connection could not be established" doesn't mean that the password is wrong. How are you trying to connect to the SQL Server instance? Did you check the logs for errors?
gibneytAuthor Commented:
Thanks for the help.  Got it figured out too.
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.