asked on

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?

gibneyt

ASKER

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?

TIA.

Tim

ASKER CERTIFIED SOLUTION