I have an issue with a SQL 2012 SP1 database that I need help with. I am not a SQL expert, so I could be overlooking something very basic.
I have a Windows Server 2012 R2 cluster that hosts multiple database instances. All the database instances are configures such that Windows Authentication works with them. Only one have I enabled for SQL Server Authentication, and it is the one I am having the problem with. I need SQL Server Authentication for this one database, so I can't eliminate that.
Using the Management Studio, I changed the database security to all SA and provided a password. But here is where is gets strange. If I launch the SQL Server Management Studio and try to connect to the Problem database via SQL Server Authentication, it fails with a timeout error. I then connect to any other database via Windows Authentication (which always works). Then I come back and try to connect again to the Problem database via SQL Server Authentication and it works. Exit the Management Studio and come back in to get the exact same results. For whatever reason, I have to first connect to any database via Windows Auth before I can open the Problem database via SQL Auth.
Of course, there is no way for the application to use such logic. Any ideas for me to try? Again, I am not a SQL expert, so I generally need step-by-step guidance to get things done in SQL.
Thanks for any direction you can provide.
. : | : . : | : . tim