cannot connect to migrated DB in SQL 2014

Hi Experts,

I have two nodes with SQL2014 and AlwaysOn configured.
With my client I cannot connect to my DB.
Do you have any hints to help me out ?
Eprs_AdminSystem ArchitectAsked:
Who is Participating?
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Ok, that command is kind of sort. It's missing more parameters.
Here are two examples:
-- Connect to a named instance with trusted connection
sqlcmd -S servername\instancename -E -d DatabaseName

-- Connect to a default instance with a SQL Server user
sqlcmd -S servername -U LoginName -P Password -d DatabaseName

Open in new window

0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
How are you trying to connect and what's the error?
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
I have a user just in DB not on the server, is it enough to login ?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Vitor MontalvãoMSSQL Senior EngineerCommented:
It's the same requisites that you need to access a non-AlwaysOn database, i.e. a SQL Server login mapped to a database.
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
when I tried sqlcmd this is not working.

Can you show me a testclient or cmd to test the login to a DB ?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Please post the command that you are trying to run.
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
sqlcmd -s servername

this is not responding...
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : A network-related or instance-specific error has occurred while establishing a connection to
 Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Login timeout expired.
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
ok solved, the username was missing on the sql instances.
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.