Logging into SQL server with SA account

Not a SQL guy at all, but trying to do my best. We have an old SQL server 2008 R2 with several databases on it, the VB apps that hit the DB use an .INI file, and in the .INI file the SQL login sa with no password is stipulated, and works fine.

Got a new SQL server, (still 2008 R2) moved the databases over, however the sa account is not allowed to have no password. So I right clicked on the sa account and set a password. Then I edited the .INI file to now include the password for the sa account. When I launch the app I get an error message that says login to sa account failed. I double checked and the password I set is the password in the .INI file, so no error there. And the sa account has the same roles and database assignments as the old SQL server.

What am I doing wrong?
thx experts...
-Bob R
bobrossi56Asked:
Who is Participating?
 
ste5anSenior DeveloperCommented:
Untitled.png
0
 
ste5anSenior DeveloperCommented:
Run SQL Profiler to see whether to login fails (maybe the password is not used) or it does connect but has different issues.

btw, it always was and is and will be a bad practice to use sa for a normal application.
0
 
bobrossi56Author Commented:
Not a SQL guy...how do I run this SQL profiler?
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

 
Vitor MontalvãoMSSQL Senior EngineerCommented:
You changed server and you only changed the SA password in the .INI file? What about the server name? Did you change it too in the .INI file? If not it still pointing to the old server.
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
You could identify the issue?
0
 
bobrossi56Author Commented:
I ran profiler as ste5an suggested and discovered some properties were not set to allow both Windows AND SQL authentication, I fixed those properties and now it works.
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
I see. The instance was configured for Windows Authentication only and you changed it to Mixed Authentication to allow SA to connect.
Good catch.
0
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.

All Courses

From novice to tech pro — start learning today.